Last updated Jul 16, 2024

Getting started

Where can I find my Rokt Account ID?

Your Rokt Account ID uniquely identifies your Rokt account when setting up API and SDK integrations, including the Event API and the Web SDK.

To find your Rokt Account ID:

1. Log in to my.rokt.com.
2. Look at the URL for your account. Your Account ID is the number immediately following my.rokt.com/accounts/.
   • For example given the URL: https://my.rokt.com/accounts/106/campaigns?startDate=2021-08-17T00:00:00.000&endDate=2021-08-24T13:34:28.463&timezone=89&currency=AUD, the Account ID is 106.

Your integration

Please select your use case to view the instructions for integration.

note

The below instructions will require development resources to complete. If you require additional assistance, please reach out to your Rokt account manager.

Launch a placement (Rokt Ecommerce)Attribute conversions (Rokt Ads)

Integration monitor for anomaly detection

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.

To read more about the the Integration Monitor, see here