Tracking lab

Map of the swimlanes

The crm-events solution overview, lane by lane, with what on this site exercises each.

The diagram

The crm-events solution overview: how events reach the CRM, one swimlane per integration type. Every lane chip in the lab links to its lane below, which lists what on this site exercises it. Lane C's four browser routes are C1 to C4.

crm-events solution overview: swimlanes A to G

Opens full size in a new tab. Source: crm-events/overview/diagrams.

  1. A. Identity

    in transition

    Okta login sends an identity event through its own SNS topic and Lambda to the CRM. Moving to the crm-events approach.

    Not exercised by this site.

  2. B. Server-side events

    current

    Host site server code publishes through crm-events-node to the AWS backbone (crm-events-infra); crm-events-delivery takes events and profile updates to the CRM.

    Tracking lab

  3. C. Browser events

    current

    crm-events-gtm brings four browser routes to the page; three send straight to the CRM, the fourth goes through the host's own server.

    Tracking lab

  4. C1. Standard Klaviyo script

    current

    Klaviyo's own browser script and its standard tracking: identify, track, client subscriptions.

    Tracking lab

  5. C2. Element attributes

    current

    Generic capture driven by data- attributes on page elements (track.js).

    Tracking lab

  6. C3. dataLayer events

    possible

    Piggybacks the window.dataLayer.push() calls front ends already make; the bridge forwards them to Klaviyo.js.

    Tracking lab

  7. C4. crm-events-beacon (browser)

    new option

    Hands events that happen as the visitor leaves to the host's own endpoint with sendBeacon; published through crm-events-node, marked untrusted (lane B).

    Tracking lab

  8. D. Real-time CLM updates

    anecdotal

    Reported but not confirmed: CLM updates reach the CRM in real time.

    Not exercised by this site.

  9. E. Data lake sync

    current

    Census (or another reverse ETL) syncs modelled data from Snowflake to the CRM.

    Not exercised by this site.

  10. F. BigCommerce connector

    current

    A vendor connector syncs Avios Shop data from BigCommerce to the CRM.

    Not exercised by this site.

  11. G. AfterShip connector

    current

    A vendor connector sends Avios Shop shipment tracking to the CRM.

    Not exercised by this site.

Full console