RVR-CRM-001
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-CRM-001
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error "RVR-CRM-001" with description "Got an Error from Criteo API" typically indicates an issue when trying to access or fetch data from the Criteo Marketing API through Rivery. This could be due to authentication issues, API request limits being exceeded, invalid request parameters, or temporary issues with the Criteo API itself.
Action Steps:
Verify Criteo Connection:
- Ensure that your Criteo connection in Rivery is set up correctly with the necessary credentials, such as the correct Client ID and Client Secret.
- Use the "Test Connection" feature in Rivery to verify that the connection is active and properly authenticated.
Check API Rate Limits:
- Review if your application has sent too many requests and hit the API limit, especially if you are receiving a 429 status code. Criteo's API limits include a restriction of 10 requests per minute for performance reporting per marketer.
Verify Request Parameters:
- Double-check that all request parameters used in the data pull (such as date ranges, dimensions, metrics) are correctly formatted and valid.
Consult Criteo's Error Message:
- Check if the error returned by Criteo API provides a more detailed message for troubleshooting and adapt your request accordingly.
Check Update Announcements:
- Ensure you are using the most recent API version and that your Rivery setup complies with any recent updates. Rivery updated its Criteo integration to API version 2023-10, which may require additional setup changes.
External References:
- Rivery's Criteo Documentation: Detailed instructions on setting up Criteo connections in Rivery.
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?