What are the major changes between your legacy APIs (MAPI and PAPI) and the new Criteo API?
What are the major changes between your legacy APIs (MAPI and PAPI) and the new Criteo API?
- A brand new Developer Portal with everything you need to connect, build, and launch your integrations (this is where you are now!)
- Developer dashboard: A one-stop shop to create and manage apps leveraging different functionalities from Criteo, such as reporting, audiences, and campaigns. You can manage multiple advertisers. Here you’ll create a new organization and can invite your teammates to this account Our new versioning policy, ensuring each version is stable for a minimum of 12 months
- A new consent management system, to specify permissions and send authorization requests to users. Each app will now request different permissions, based on its purpose. These can be read or manage permissions. Your end-users will see which permissions your app is requesting
- For Partners: A Criteo connector for generating consent URLs from your own platform
What are the improvements to the API itself?
What are the improvements to the API itself?
-
Along with the overall changes to the Criteo API’s functionality, we are also improving specific endpoints’ capabilities:
- Updated Statistics endpoint, with 100+ metrics, including app and store campaigns, so you can build custom reports or connect with your own platforms
- Updated Transaction ID report, now allowing multiple advertisers and additional time zones
- Automate campaign management with APIs for budget, ad sets, audiences, and more
How will the new API impact my current integration with Criteo?
How will the new API impact my current integration with Criteo?
What resources are available for the migration?
What resources are available for the migration?
How long will the migration take my developers?
How long will the migration take my developers?
If I connect to the API through a partner, what do I need to do to migrate?
If I connect to the API through a partner, what do I need to do to migrate?
Will the MAPI and PAPI deprecation impact my Shopify or ECP integration?
Will the MAPI and PAPI deprecation impact my Shopify or ECP integration?
Why would I want to use the API?
Why would I want to use the API?
What do I need to use the API? What resources are needed?
What do I need to use the API? What resources are needed?
- Familiarity with APIs: The Criteo API system uses industry standards. If you are using similar APIs from your other advertising partners, you will likely already have the required skills in your dev team to use them. In addition, we are evolving our developer program to provide your developers with all the tools that they will need to use our APIs.
- Use cases: It will require a different level of effort to retrieve a custom report than to programmatically control your entire campaigns. We suggest going step by step, starting with the reporting use case. To do so, your developers can first create a developer account, start testing the API, and then integrate it into an automation flow. The first two steps tend to take our clients an average of two hours and that the last step could take one or two days. These numbers include both large clients and small clients with more limited resources. Starting from there, it will be easier to start using other endpoints for more advanced use cases. Once your dev team is familiar with their first Criteo API call, the marginal cost to use the other endpoints will be lower.
- Activating through a partner: In some cases, you could indirectly use Criteo APIs through a partner. For example, you could use reporting Criteo APIs to build custom reports within your reporting platform of choice or your agency’s in-house reporting tool. Or you could use Criteo APIs to push an audience through your CDP. In those cases, the technical resources needed to integrate Criteo APIs will be absorbed by partners or agencies.
Will I be charged for using the API?
Will I be charged for using the API?
How can I get started?
How can I get started?
What other functionality will be added to the Criteo API?
What other functionality will be added to the Criteo API?
If I am using your legacy APIs (PAPI & MAPI), when do I need to change my integration?
If I am using your legacy APIs (PAPI & MAPI), when do I need to change my integration?
- Registering an organization and an app
- Swapping your MAPI credentials with the app’s credentials
- Modifying your existing MAPI paths (for example, from https://api.criteo.com/marketing/v1/audiences to https://api.criteo.com/legacy/marketing/v1/audiences)
When will v2020.07 be deactivated?
When will v2020.07 be deactivated?
- /legacy/marketing/v1/advertiser/{advertiserID}/categories
- /legacy/marketing /v1/advertiser/{advertiserID}/categories/{categoryHashCode}
- /legacy/marketing /v1/campaigns/{campaignId}/categories
- /legacy/marketing /v1/campaigns/{campaignId}/categories/{categoryHashCode}
- /legacy/marketing /v1/categories
- /legacy/marketing /v1/campaigns/bids (used for category bidding)
When is category bidding going to be available in the new API?
When is category bidding going to be available in the new API?
How do authorization requests work?
How do authorization requests work?
What is the versioning policy? How often do I need to make changes?
What is the versioning policy? How often do I need to make changes?
Currently, you can share a consent URL directly with your clients on a 1:1 basis or (info here about new consent URL generation). In the future, we plan to have discoverable ways for users to explore available integrations right from within Criteo. Please reach out to us If you’d be interested in this feature.
How far back can we pull data through the API?
How far back can we pull data through the API?