PartnerStack Integration - Everflow Helpdesk

This integration passes conversion data from your PartnerStack account into Everflow using a postback, with Zapier acting as the bridge between the two platforms.

PartnerStack's webhooks only support the POST method, while Everflow postbacks require the GET method. Because of this difference, Zapier is required to relay the data from PartnerStack into Everflow, whether you are using a Vendor account or a Partner account.

For more on PartnerStack - [Click Here]

ImportantBefore implementing this integration, you must have a conversion in PartnerStack that includes an sid1 value. Without an sid1 value, the data cannot be mapped in Zapier.

Prerequisites

Before you begin, make sure the following are in place:

A PartnerStack account (Vendor or Partner).

A Zapier account, used to relay conversion data from PartnerStack to Everflow.

A conversion in PartnerStack that includes an sid1 value, so the data can be mapped in Zapier.

Append the sid1 Value to Your Landing Page

Append &sid1={transaction_id} to the end of your default landing page URL. This passes the Everflow transaction ID through to PartnerStack so the conversion can be matched back to the original click.

The sid1 value is what links a PartnerStack conversion back to the corresponding Everflow click, so it must be present on every conversion you want to track.

Vendor Account Setup

If you are using a PartnerStack Vendor account, a dedicated Zap Trigger is available that can be connected directly to the Everflow Zap Action.

Create a new Zap with the PartnerStack trigger

In Zapier, create a new Zap and select the PartnerStack trigger.

Connect your PartnerStack Vendor account

Connect your PartnerStack Vendor account to the trigger so Zapier can receive conversion data from PartnerStack.

Add the Everflow Create Conversion action

Add the Everflow Create Conversion action as the next step in the Zap.

Map the data into the Everflow action

Map the data from the PartnerStack trigger into the Everflow Create Conversion action, including the sid1 value, so the conversion is recorded against the correct click in Everflow.

Partner Account Setup

If you are using a PartnerStack Partner account, the dedicated PartnerStack trigger is not available. Instead, use a Zapier webhook that you place as a postback inside your Partner account using the Transaction event type. For reference on PartnerStack postbacks, see the PartnerStack postbacks documentation.

Create a new Zap with the Webhooks trigger

In Zapier, create a new Zap and select Webhooks by Zapier as the trigger.

Choose the Catch Hook trigger event

Choose the Catch Hook trigger event. Zapier will generate a unique webhook URL.

Copy the webhook URL

Copy the webhook URL generated by Zapier.

Add the webhook as a Postback in PartnerStack

In your PartnerStack Partner account, add the copied webhook URL as a Postback using the Transaction event type.

Add the Everflow Create Conversion action

Back in Zapier, add the Everflow Create Conversion action as the next step in the Zap.

Map the data into the Everflow action

Map the data from the webhook into the Everflow Create Conversion action, including the sid1 value, so the conversion is passed into Everflow and matched to the correct click.

NotePartnerStack postbacks use the POST method, while Everflow postbacks require GET. Zapier handles the conversion between the two methods, which is why it is required for both Vendor and Partner account setups.

Did This Help You Today?

Yes

Next in This Series

Learn how to integrate with PartnerStack using conversion postbacks relayed through Zapier.

Lorem Ipsum Dolor Sit

Overview

Prerequisites

Append the sid1 Value to Your Landing Page

Vendor Account Setup

Partner Account Setup

Looking for extra support?