Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The default service always supports the analytics context. If using multiple services and only one is used for visitor behavior, make it the default.

Send2CRM also supports visitor identification and updates to secondary services, allowing behavior to be synced across multiple CRM instances.

Considerations

Identifying a visitor to multiple services can be complex as the source of truth becomes distributed.

  • If any single service applies an Ignore status to the visitor, this will override other services.

  • Send2CRM tracks which services recognize the visitor:

    • Identified visitor updates are sent to services where unknown at a reduced frequency.

    • An identified visitor will only become un-identified again if unknown to all services.

  • A shared visitor id is used across services to keep them in sync. Ensure that this is maintained if syncing the visitor records externally.

Enable Analytics Context

The analytics context must be set for all secondary services that should handle visitor behavior.

// Specify the analytics context when registering a secondary service.
let contexts = ['analytics'];
send2crm.services.register('myAlias', hostName, apiKey, contexts);

// The context may also be added after registering.
send2crm.services.addContext('myAlias', 'analytics');

  • No labels