Cross-navigation enrichment

This enrichment parses the extended cross-navigation format in the _sp querystring parameter, and attaches a cross_navigation entity to an event.

Check out the cross-navigation page to learn why this can be useful.

The extended cross-navigation format is _sp={domainUserId}.{timestamp}.{sessionId}.{subjectUserId}.{sourceId}.{sourcePlatform}.{reason}. The domainUserId and timestamp fields will always be present, but some of the other fields may be null or empty. They're configured within the tracker.

If this enrichment isn't enabled, Enrich parses the _sp querystring parameter according to the short format, _sp={domainUserId}.{timestamp}

Event fields always populated

The pipeline will always populate the refr_domain_userid and refr_dvce_tstamp enriched event fields, even if this enrichment isn't enabled.

Configuration#

• Schema
• Example

config/enrichments/cross_navigation_config.json

loading...

View on GitHub

Testing with Micro

Unsure if your enrichment configuration is correct or works as expected? You can easily test it using Snowplow Micro on your machine. Follow the Micro usage guide to set up Micro and configure it to use your enrichment.

Input#

This enrichment extracts the _sp querystring parameter from the page_url field from the Snowplow event.

Output#

This enrichment adds a new derived entity to the enriched event based on this schema.

Enrich always populates the refr_domain_userid and refr_dvce_tstamp enriched event fields.