Skip to main content
Integration: 29 Next

This article gives instructions for integrating with 29 Next, including the app configuration, URL parameter passing, & API implementation.

Chris Chimento avatar
Written by Chris Chimento
Updated today

Overview

29 Next is an ecommerce platform designed for digital marketers and DTC brands.

This guide walks you through setting up the 29 Next + Everflow integration, configuring proper click tracking parameters, and establishing server-to-server communication for accurate conversion reporting.

By following these steps, you'll create a seamless data flow between your 29 Next storefront and Everflow, enabling you to measure Offer effectiveness, optimize your spend, and properly compensate your Partners based on the Conversions they generate.

Step 1: Create the Offer in Everflow

Before configuring your 29 Next storefront, you'll need to set up the tracking environment in Everflow:

  • You will start by creating an Offer in Everflow.

  • The Conversion Method will be Server Postback.

  • When configuring the Base Destination URL, make sure it contains the evclid parameter with the Transaction ID macro: ?evclid={transaction_id}

Importnat Note

The evclid parameter must begin with a ? if it's the first parameter, or an & if it follows other parameters.

Step 2: Setup Everflow Integration for Your Storefront

Once your Everflow offer is created, you'll need to set up the integration in your 29 Next admin panel:

  • Navigate to Apps > Everflow.

  • Input your Everflow account credentials

  • Click Save.

Source Attribution on an order-level is populated by values passed via querystring parameters. The Everflow Click ID (Transaction ID) should be passed using the evclid parameter on links to your storefront.

The Everflow App uses the S2S (Server to Server) conversion method with an order. The S2S conversion method will enable the following values to be passed back on a conversion event into Everflow.

  • order amount

  • order currency

  • Everflow NID

  • order number

  • transaction id

Important Notes

  1. Postback Delay: Use the Everflow Postback Delay setting to allow up to 10 minutes for post-checkout Upsells Revenue generated in a single customer session to be accounted for in the conversion event postback.

  2. Include Tax in Conversion Value: Order totals sent to Everflow on conversion events are tax exclusive by default. Enable the Include Tax in Conversion Value setting if you want to post the order total inclusive of tax to Everflow.

  3. Verification Token: An Everflow Verification Token can be added if one is being enforced at the corresponding Advertiser's Offers.

Step 3: Set up Everflow Postbacks via Admin API

  • For orders created via the Admin API orders_create method, you must pass the everflow_transaction_id as a string into the Source Attribution Metadata field on your API call.

  • Orders created with this ID will trigger the S2S postback to Everflow, and associate the conversion events back to Everflow.

  • The everflow_transaction_id is equivalent to the "transaction_id" that Everflow generates on a click to your URL.

Example Source Attribution Meta with Everflow Transaction ID

"attribution": {
"metadata": {
"everflow_transaction_id": "string"
}
}

Important Note

Test Orders will not fire an S2S postback to Everflow.

Did this answer your question?