Skip to main content

Integration monitor

Overview​​​

Rokt’s solutions humanize the customer experience through relevance and play an essential role in the customer journey. As Rokt becomes more critical in your customer journey, so does the importance of your integrations with Rokt. Although Rokt takes excellent care to ensure the quality of integrations, they are not immune to anomalies. Potential sources of anomalies include:

  • Integration errors or introduced bugs,
  • Unsupported browsers,
  • Site changes,
  • CDN outages,
  • Custom plugins, and
  • Network failures.

These anomalies can harm the customer experience by not showing critical components powered by Rokt or result in erroneous reporting, resulting in lost ancillary revenue, lowered conversion rates, and lower LTV.

Advertisers use the Integration Monitor to ensure they integrate all conversion data to Rokt. For example, if you are meeting your CPA targets with Rokt and discover that you are not integrating all conversion data correctly, this represents an opportunity to reduce your CPA and unlock additional growth.

Partners use the Integration Monitor to ensure Rokt's SDK has maximum coverage across all transactions. For example, uncovering 1M additional transactions Rokt's SDK was previously not enabled on represents an incremental $200,000 revenue, at $0.20 per transaction.

Integrating a secondary source of event data will allow you to make sure that your integrations work as expected and quickly identify when and why an unexpected discrepancy occurs.

Integration Process​​

Rokt can now connect to any of your systems containing transaction or conversion data, such as CDPs, CRMs, or analytics platforms like Google Analytics. Rokt requires API credentials to be provisioned for the desired system; from there, Rokt will handle the rest, and no coding is required.

To get integrated:

  1. Provide your account manager with a list of systems you use that contains either session or conversion data. These systems are commonly analytics tools, attribution systems, and CDP.
  2. Your account manager will provide instructions for provisioning an API key and specifying the data query parameters to be shared with Rokt.
  3. Rokt will perform QA and configure monitors and the relevant alerting systems when the solution is set up.

Example​​

A secondary data source you may choose to integrate with Rokt is Google Analytics (GA). GA records the number of user sessions that occur on your website. Rokt can integrate with GA to receive the number of sessions to be checked against Rokt’s records from the Rokt Web SDK. A discrepancy between the session numbers would imply something has gone wrong and can alert Rokt to conduct an investigation.

Conclusion​​

Secondary data sources provide extra support by ensuring integrations work as expected, identify discrepancies promptly, and prevent suboptimal customer experiences, erroneous reporting, and lost ancillary revenue.