From the perspective of the Optimize platform, a Push integration is one where we're sending data out to another system.

Most commonly, push integrations are used to send experiment views into Analytics / Insights platforms, such as Web Analytics, Session Recording, Heatmapping, etc., so that you can get further insights about the performance of your experiment from those platforms.

There are some generic, toggleable settings in all Push integrations. These are detailed as follows:

By default, we send experiment views every time someone views an experiment, but for some websites with a high degree of traffic that browsers around the website, and for customers who are running many sitewide tests, this could drastically drain your API call budget.

This feature allows you to send data only once per session per test, thus limiting the calls whilst still maintaining your ability to generate the same reports.

​

Running a short side-wide campaign, that's not an experiment just content-delivery? You might not care about the impact of it in your Analytics platform given all users are seeing that content.

This is a straightforward way to exclude the sending of data for specific tests/targets you're running, whilst leaving everything else intact, thus again not inflating your API call budget for no reason.
​

Some people like to track data for Completed tests (100%s, optimals), some feel it's not necessary beyond having run the test.

The option is there to pick your journey, and send data if you want to, or limit it if you don't.