Revjet Sync
What is RevJet?
RevJet is a creative experience platform designed to optimize and scale digital advertising across display, video, social, and other formats. It provides tools for managing, testing, and personalizing ad creatives to improve performance and ROI. RevJet also supports robust data integrations, enabling marketers to synchronize identifiers and enhance attribution accuracy. Through ID syncs like MetaRouter's, RevJet can better match users to ad exposures for more precise targeting and measurement.
Product Type: Personalization
Integration Type: ID Sync
Capabilities
- Captures
revjet_vid
by sending a GET request to RevJet’s sync endpoint. - Enables audience matching and targeting across RevJet-served media.
- Refreshes stored identifiers whenever a new identity call is made.
- Stores failed sync attempts separately to manage retry behavior.
- Drops the
trx
cookie via syncinjector for session continuity.
Sync Details
-
IDs:
revjet_vid
– A unique user identifier provided by RevJet to track user engagement and support audience targeting.
-
Description:
- The sync captures
revjet_vid
from a RevJet GET request tohttps://pix.revjet.com/idsync/metarouter/1?metarouter_id=[MATCH_ID]&rformat=text
. - Each value is stored in first-party storage for a configured duration.
- Values are refreshed when new data is detected, including when identity calls are re-fired.
- Failed fetch attempts are tracked with a failure cookie to limit unnecessary retries.
- The identifiers are added to server-side event payloads for attribution or targeting.
- The sync captures
-
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 thecontext.providers
property within the event's JSON payload.{ "revJet": { "revjet_vid": "abc-123" } }
-
Cookie Name:
- Cookie:
_meta_revjet_revjet_vid, _meta_revjet_vid_failure, _meta_revjet_fix
- IndexedDB:
[your storage prefix]_revjet_revjet_vid, [your storage prefix]_revjet_vid_failure, [your storage prefix]_revjet_fix
- For a general guide on ID Sync validation, see here.
- Cookie:
Sync Setup Guide
1. Add a RevJet Sync in MetaRouter
To gather the revjet_vid
, you must add a RevJet sync.
- 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.”
- In the Identity Syncs section, select the RevJet sync.
- Fill out the following fields:
- Cookie Lifetime (in days) – Duration before the stored
revjet_vid
value expires. Example:30
- Failure Cookie Age (in days) – Number of days to wait before retrying a failed sync. Example:
1
- API Timeout (in milliseconds) – Time to wait before aborting a sync request. Example:
5000
- Fire On ReSync – Determines if the sync should fire again with each identity call. Example:
true
- Cookie Lifetime (in days) – Duration before the stored
- Scroll down and click the Save and Build File button.
- Deploy your AJS file to propagate changes to your web property.
Updated 1 day ago