Everflow Reference

Send conversion events directly to Everflow.

The Everflow destination is currently in Early Access. Please contact [e-mail] for more information about this integration.

Destination Info

• Supports Track calls

• Supports HIPAA mode

• Supports forwarding from the Google Tag Manager Integration

• Refer to this destination as Everflow in the Integrations object

  • If you've configured multiple Tag IDs, you can choose a specific one by suffixing the Network ID, such as: Everflow::1234123456. You can retrieve this value from the Everflow configuration page for the Network ID of interest.

• Connection Modes:

	Client-side	Server-side
Web
Mobile
Server

This is a reference document for the Everflow destination. For information on how to set up this integration, see the Everflow Quick Start Guide.

Events

Required Properties

Freshpaint Property	Everflow Parameter	Type	Requirement	Description
$ef_transaction_id	transaction_id	string	At least one of $ef_transaction_id and coupon is required.	The Everflow transaction ID (click ID) captured automatically from the landing page URL or through the Everflow transaction ID cookie. Required for click-through attribution.
coupon	coupon_code	string	At least one of $ef_transaction_id and coupon is required.	The coupon code tied to the partner. We do not automatically capture this value like how we capture the transaction ID. The coupon code should be sent within a track event when the order is placed.
$ip	user_ip	string	Recommended	The IP of the user.
$user_agent	user_agent	string	Recommended	The user agent of the user.

Troubleshooting

Conversion events not showing up in Everflow: For an event to show up as a conversion event it must have a $ef_transaction_id or coupon property. You can validate that events going to Everflow have at least one of these properties using the Freshpaint Liveview.

Events show "Missing Required Property" in Event Verification: The $ef_transaction_id and coupon properties were absent when the event was processed. If it's occurring on events that should have the transaction ID, check that the Freshpaint snippet is installed on the landing page and that $ef_transaction_id isn't being stripped by redirects or link-shorteners before the visitor lands.

The Tracking Domain URL is rejected during configuration: The Tracking Domain must begin with http:// or https://. Bare domains without a scheme (e.g. tracking.example.com) are not accepted.