📘
This integration is currently in beta. Contact your MetaRouter support team to get started.

What Is EngageFront?

EngageFront is a demand-side platform (DSP) used by advertisers and agencies to run multichannel programmatic campaigns. Using proprietary first-party weather and location data, it creates highly targeted audience segments and dynamic triggers for campaign activation. The platform supports display, video, and native formats and provides reporting tools that enable real-time campaign optimization. EngageFront helps marketers improve targeting accuracy and attribution across the full funnel.

Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Full-Funnel Events

Capabilities

Sends events to EngageFront’s server-side POST endpoint.
Attaches EngageFront identity values (twn_id, attr_cookie) to events through identity sync.
Preserves IP, user agent, and referrer for weather- and location-based targeting.

Considerations

twn_id and attr_cookie may be returned as null in any combination; all cases are valid and should still be forwarded.
High-volume internal testing showed no rate limits, but monitoring is recommended when scaling.
The attribution identifier uses a placeholder output key (ef_[ADD_campaign_OR_advertiser]_id) in the starter kit. This must be manually replaced with the correct key—either ef_campaign_id or ef_advertiser_id—based on use case. The corresponding value must be a static string ID provided by EngageFront, entered directly in the enrichment field.

Limitations

Rich e-commerce fields are not processed by EngageFront’s current event ingestion API.

Identity Sync

Sync Available: Yes
Required for Starter Kit: Yes
Prerequisites: Weather Network cross-domain GUID present for EngageFront identity resolution
Documentation: See Additional EngageFront Documentation

Sync Details

Retrieves twn_id and attr_cookie from EngageFront’s sync endpoint via a fetch-based sync.
Refreshes values automatically upon expiration.
Adds resolved IDs to outbound events under context.providers.engageFront.

Starter Kit Setup Guide

1. Deploy the EngageFront Sync

To collect the sync values (twn_id, attr_cookie), you must implement an EngageFront ID sync. Refer to the following documentation to complete the setup: EngageFront – ID Sync Guide.

2. Gather Credentials

Ask vendor representatives for the following credentials:
- API Key — Enables authentication on EngageFront’s events endpoint.
- Campaign ID or Advertiser ID — A static identifier required for attribution. This value must be entered into the enrichment field and determines whether the integration uses ef_campaign_id or ef_advertiser_id.

3. Add an EngageFront Integration

From the integration library, add an EngageFront integration. Then, fill out the Connection Parameters:

Connection Parameter	Description
`API_KEY`	API key used in the Authorization header for sending events.

4. Configure Event Mapping

MetaRouter provides all of the event mappings that EngageFront integrations typically require. You may add custom events, parameters, or mappings in accordance with EngageFront’s API documentation.

5. Deploy to Pipeline

In the Pipelines tab, add your EngageFront integration.
Select the correct integration revision.
Click Add Integration and finalize deployment.

Event Mappings

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output Key	Description	Expected Input
`ef_[ADD_campaign_OR_advertiser]_id` Required Example output: `ef_campaign_id`	String: Campaign or advertiser ID. NOTE: Please ensure you replace output key`[ADD_campaign_OR_advertiser]` with `campaign` or `advertiser` in all lower case. Ex. `ef_campaign_id`	Enrichment – static identifier
`client_ip` Required	String: IP address of the user.	`context.ip`
`user_agent` Required	String: User agent for device and browser classification.	`context.userAgent`
`referer` Required	String: Referrer URL.	`context.page.referrer`
`timestamp` Required	String: Event timestamp in expected vendor format.	Expression – adjust RFC3339 to EngageFront's expected format
`event_name` Required	String: Event name.	Expression – Derives the vendor event name using playbook logic: if `input.type` is `"track"`, the expression lowercases `input.event` and replaces spaces with underscores; otherwise it returns `input.type`.
`twn_id` Required	String: EngageFront ID from sync.	`context.providers.engageFront.twn_id`
`attr_cookie` Required	String: Attribution cookie from sync.	`context.providers.engageFront.attr_cookie`

Event Specific

EngageFront accepts all events; no event-specific mapping tables are required for this Starter Kit.
Event filtering may be customized at any time through the playbook allow/deny list.

Required & Recommended Identifiers

Attribute	Example	Sync Injector Required?
`twn_id` Required	`1cfa9ad9-3f85-412f-8e4c-ac513170d718`	Yes
`attr_cookie` Required	`fa0567b1-f0d2-428f-8d5b-9f3add941959`	Yes
`client_ip` Required	`203.0.113.5`	No
`user_agent` Required	`Mozilla/5.0 (Windows NT 10.0; Win64; x64)`	No

Integration Validation

Please contact your EngageFront representative to validate incoming data.