Help Center

| Submit or View Help Requests | Developer Docs |

View desktop instructions
View mobile app instructions
Product Data Change Postback Notifications FAQs

If you want to receive real-time notifications whenever changes are made to a product catalog you have access to, you can set up a Product Data Change Event Notification.

What is an event notification?

Event Notifications can update a third-party system in real-time via HTTP server calls. If you have an event notification set up and a trigger event occurs (like your partnered brand modifying an actor you drove), will send a postback to your provided URL with a notification.


Event notifications, postbacks, and webhooks are all different terms for the same process in the platform. For consistency's sake, the rest of this article will use the term "postback."

How do product data change postbacks work?

Product data change postbacks work by updating you whenever an update is made to a product catalog you can view. For example, if your partnered brand updates their catalog to reflect that some items are now out of stock, you would receive a postback.

Why wouldn't I just use's API?

While our API is perfectly suitable to provide you with the same information, there are some characteristic and restriction differences between our API and our postback system that would likely make postbacks a preferable solution for you. These include the following:

  • Postbacks happen in real-time. Postbacks are generated by and received by you within 10 minutes of a non-standard event happening.

  • Postbacks have access to more conversion data. Even if you don't see the data point you need in our UI (or our developer reference sheet) when setting up your postbacks, we likely have the data point available if you reach out to your Publisher Account Manager (or contact support).

  • Postbacks do not have rate limits. When you use's API, you are subject to rate limits we have placed on our system. Specifically, when using our API, you are limited to 1000 API requests for most endpoints, whereas postbacks have no such limit.

Are postbacks reliable?

Yes! makes use of postbacks in some of our own tracking solutions. You don't need to meet any special criteria to utilize postbacks, you don't face any rate-limiting, and will continue to try to reach your server until we receive a 200 or 201 response (meaning you received the information with no issues).

When we perform maintenance of our postback system, you will be notified and postbacks will be paused. However, as soon as we complete the maintenance, we will immediately begin catching your system backup.

However, if you notice a delay with receiving postbacks, like an action was modified and you haven't received a postback in over an hour since the modification occurred, contact support.

What security measures does use for postbacks?

When using postbacks, you will establish the destination to which you want the calls to be sent. Because of this, because stores the data on our back-end, and because performs a server-to-server call when we send the data, there is no way to intercept the data while it is in transit.

If you want, we can create a custom header that conveys another set of credentials to include in the postback calls sends you. You cannot create this header in the web app, so reach out to your Publisher Account Manager (or contact support) to notify us that you want this header created.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.