Identity Syncs

🚧

The Identity Sync pages are under construction.

What Are Identity Syncs?

Identity Syncs are part of the MetaRouter integration ecosystem, designed to unify user identities across different parts of your website or app, ensuring that each event is accurately associated with the same individual. Rather than relying solely on basic cookies or fragmented IDs, Identity Syncs apply specialized logic to maintain a consistent user identity across pages and sessions. This approach is critical for accurate analytics, personalized experiences, and more effective marketing.

Sync Injector

Identity Syncs utilize the Sync Injector, a MetaRouter component that dynamically injects user identifiers—such as hashed email addresses, custom user IDs, or vendor-specific tokens—directly into the event stream. By automatically capturing and associating these identifiers, the Sync Injector eliminates the need for multiple tracking scripts or manual ID mapping. This ensures that each event is correctly attributed to the appropriate user, reducing operational overhead and enabling more efficient data analysis.

For more details on the Sync Injector, refer to this documentation.

Integration Ecosystem

Identity Syncs can function in different ways, depending on the use case:

• With a Starter Kit – Combines identity resolution with data routing and event transformation.
• As a Standalone Solution – Unifies user IDs without additional data transformation. These IDs can work alongside other MetaRouter components to manage both event transformation and identity enrichment.

This flexibility allows Identity Syncs to support various data strategies while ensuring accurate and consistent user identification.

Validating Identity Syncs

Cookies

• Open Developer Tools and expand the Cookies section under Storage. Click on your domain.
• You should see your ID sync appear, typically formatted as _meta_[cookie name]_[suffix].
• The cookie name generally resembles the name of the integration. For more specific naming conventions, refer to the documentation for the ID sync you’re working with.
• The suffix often describes the sync type or vendor identifier — for example, a click ID name.
• Click on the cookie name to view the value of the synced ID.

IndexedDB

• If your implementation uses IndexedDB, follow this path: Developer Tools → Application → Storage → IndexedDB.
• Locate the expandable menu named after the prefix you configured in MetaRouter’s File Builder under Advanced Settings.
• Expand the menu, then expand the syncs object and click on name to find the cookie name.
• Cookie name format: [your storage prefix]_[cookie name]_[suffix].
• Under the Value column, expand the object to see the synced ID.
• For more details on IndexedDB, Advanced Settings, and the storage prefix, see this guide.

Custom Identity Syncs

If a required identity sync is not available in the Sync Injector library, you can request it by contacting your MetaRouter CSM. Alternatively, you can build your own custom identity sync. For more details, see this guide.

Best Practices

Default values in the ID sync setup (e.g., cookie lifetime) are based on vendor best practices; however, we strongly recommend confirming all values and configurations internally and with your vendor's Customer Success Manager (CSM) to ensure alignment with your specific use case.