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: ID Sync

Capabilities

• Captures twn_id and attr_cookie from a vendor API response using a fetch request based on a 1:1 mapping to the Weather Network cross-domain GUID.

Considerations

• The sync requires the Weather Network cross-domain GUID to be present, as twn_id and attr_cookie are resolved based on a 1:1 identity mapping to that GUID.

Sync Details

• IDs:

  • twn_id – A unique EngageFront identifier that maps directly to the Weather Network GUID and is used for cross-domain identity resolution.
  • attr_cookie – An attribution identifier returned by EngageFront for campaign and engagement tracking.

• Description:

  • The sync captures twn_id and attr_cookie from a GET request to the EngageFront endpoint.
  • Each value is stored in first-party storage for a duration defined by the Cookie Lifetime setting in the UI.
  • Values are refreshed when the existing stored values expire.
  • The identifiers are added to server-side event payloads for attribution or targeting.

• Response Example:

  JSON

  {
    "twn_id": "1cfa9ad9-3f85-412f-8e4c-ac513170d718",
    "attr_cookie": "fa0567b1-f0d2-428f-8d5b-9f3add941959"
  }

• Server-side Event Payload: Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

{
  "engageFront": {
    "twn_id": String,
    "attr_cookie": String
  }
}

• Cookie Name:
  • Cookie: _meta_engageFront_twn_id, _meta_engageFront_attr_cookie, _meta_engageFront_attr_cookie_failure, _meta_engageFront_twn_id_failure
  • IndexedDB: mr_engageFront_twn_id, mr_engageFront_attr_cookie, mr_engageFront_attr_cookie_failure, mr_engageFront_twn_id_failure
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

2. Add a EngageFront Sync in MetaRouter

To gather the twn_id and attr_cookie values, you must add a EngageFront sync.

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the EngageFront sync.
3. Fill out the following fields:
   1. Cookie Lifetime (days) – How long a synced identifier remains in first-party storage. When expired or no longer detected, the sync will re-trigger.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.