Skip to main content

Outbrain Server

Updated over a week ago

⭐ Available in the following bundle: Core Bundle (incl. in all plans)

⭐ Available on the following plans: Agency, Business

👀 Not sure which plan you're on? Check your subscription here.

For native advertisers using Outbrain by Teads, seamless tracking is essential to maximize campaign performance. Our integration makes it easier than ever to measure conversions directly within Outbrain, giving you accurate insights to optimize your spend, boost engagement, and drive more meaningful results—all without extra complexity.

Logo Outbrain PNG Transparent Logo Outbrain.PNG Images. | PlusPNG

💡 Server-to-server tracking allows you to measure conversions without depending on browser-based pixels.


Setup

Step 1: Set up Conversion Event

  1. Go to your Outbrain Campaign Manager and click on Conversions on the left.

  2. If you want to use an existing conversion event, you can find its name in the events overview.

  3. If you're creating a new conversion event, click on Create Conversion on the top right and choose Server to Server as your data source. Click on Next.

  4. Under Conversion type, select the event category, e.g. Lead and also insert a unique Event Name. Then click on Create Conversion.

Step 2: Connect your flow

  1. In Heyflow, click on Integrate to access your integrations.

  2. Under Analytics, select Outbrain.

  3. Enter the copied Event Name. It must match exactly the event name in your Outbrain conversion setup (case-sensitive).

Step 3: Set up Conversion Value & Currency (Optional)

  1. Optionally, you can insert a Conversion Value, which is a static monetary value for your conversion event.

  2. Also, you can optionally select the Currency for your conversion value from a list of all available currencies in Outbrain.

Step 4: Set Live

Click on Connect and republish your flow. Congratulations, you've set up your Outbrain integration in Heyflow!


Troubleshooting

I don't see any events

There may be several reasons for this:

  • Changes not published yet: First, make sure that your flow has been republished after you have made changes to the integration.

Did this answer your question?