Everflow Integration

Location: Campaigns; Publishers; Webhooks → Outgoing; Numbers → Snippets; Integrations → Reporting (chart icon); Custom Tags

Use this when you need Everflow to receive Moja conversion postbacks with the correct offer, affiliate, and (for click‑level tracking) transaction ID.

Moja does not auto‑configure an Everflow postback URL and does not sync offers or affiliates from Everflow. You enter the IDs in Moja, then send them on an outgoing webhook that you create, attach to the campaign, and point at Everflow.

What this integration does

Stores an Everflow Offer ID on the campaign
Stores an Everflow Affiliate ID on the publisher
Expands those values as webhook tags [EF_OFFER_ID] and [EF_AFFILIATE_ID]
For dynamic numbers, accepts an Everflow transaction ID from the landing page through the Moja snippet (window._moja_tags) or from a URL parameter

Before you begin

An Everflow offer and affiliate, plus the postback URL Everflow gives you
A Moja campaign and a publisher for that affiliate
For click‑level tracking: a Moja snippet with number replacement and Capture User Data enabled, plus a number pool. See DNI, tracking tags/snippets, and number pools.

Static numbers (one tracking number per affiliate)

Use this when each affiliate has a dedicated Moja number. Everflow treats this as a clickless conversion: offer ID + affiliate ID, no transaction ID.

1. Add the Offer ID to the campaign

Go to Campaigns and open the campaign
Scroll to the Everflow Integration panel
Enter Everflow Offer ID
Save the campaign

2. Add the Affiliate ID to the publisher

Go to Publishers and open the publisher for this affiliate
Scroll to the Everflow Integration panel
Enter Everflow Affiliate ID
Save the publisher

The fields are optional in Moja. Leave them blank if you are not using Everflow. For a complete static postback, both values must be present on the call: offer from the campaign, affiliate from the publisher that owns the inbound number.

3. Create the outgoing webhook

Go to Webhooks → Outgoing (not Settings)
Create a webhook
Set the event to call.converted
Set method and URL to the Everflow postback Everflow provides (often GET)
Put Moja tags in the URL, query, or body. Typical placeholders:

oid=[EF_OFFER_ID]&affid=[EF_AFFILIATE_ID]&amount=[REVENUE_PAID_OUT]

Exact parameter names come from Everflow. Moja only expands the bracket tags. Use single‑bracket tags such as [EF_OFFER_ID].

4. Attach the webhook to the campaign

Creating the webhook does not send traffic. Open the campaign and attach it under Outgoing webhooks. Live converted calls fire only after attach. Details: Outbound Webhooks Guide and Send call data to more than one outbound webhook.

Dynamic number pools (click‑level transaction ID)

Use this when the landing page uses a Moja number pool and you need Everflow’s click transaction ID on the conversion.

Complete the static steps above first (offer ID, affiliate ID, webhook, campaign attach).

1. Install the Moja snippet

Add the Moja snippet to the landing page <head>. Enable number replacement and Capture User Data. Assign the pool and Number to Replace. This is Moja DNI, not an Everflow‑only snippet. See DNI, tracking tags/snippets, and number pools.

2. Pass the Everflow transaction ID into Moja

If the visitor reaches the page on an Everflow redirect and the transaction ID is already in the URL, Moja stores it with the other URL parameters. You can send the whole set with [URL_PARAMETERS].

If there is no URL parameter (common with Google Ads direct links), Everflow’s JavaScript has the transaction ID and you must push it into Moja. After both scripts are on the page:

<script>
  window._moja_tags = window._moja_tags || [];
  window._moja_tags.push({ ef_transaction_id: TRANSACTION_ID });
</script>

Replace TRANSACTION_ID with the value Everflow’s script exposes. You can push before or after the Moja snippet initializes; Moja buffers late pushes and syncs them on heartbeat.

Installing only Everflow’s snippet does not populate Moja tags.

3. Create a Custom Tag so the value can be posted

Landing‑page custom tags are kept on the visit only if a matching Custom Tag exists in the org. Create a Custom Tag named ef_transaction_id (lower‑case). Then use [EF_TRANSACTION_ID] on the webhook. Tag matching is case‑insensitive; keep the stored name lower‑case.

4. Add the transaction ID to the Everflow postback

Include whatever query name Everflow requires for the transaction / click ID, for example:

transaction_id=[EF_TRANSACTION_ID]

Where to verify

Integration Reporting — on the Integrations page, click Reporting (chart icon), then open the call’s tracking details. Custom Tags shows values pushed with window._moja_tags. URL parameters show query‑string values.
Webhooks → Outgoing Requests — confirm the converted‑call request, expanded tags, and Everflow HTTP status.
Call Logs — confirm the call converted. The webhook event is call.converted, not every completed call.

There is no dedicated Everflow dashboard in Moja and no Custom Tags column on the main call table. Exporting Custom Tags from Integration Reporting is the visit‑level view, not a separate Everflow report.

What this does not do

Does not build or host the Everflow postback URL for you
Does not sync offers or affiliates from Everflow
Does not fire a postback unless an outgoing webhook is created, uses the right event, and is attached to the campaign
Does not turn an Everflow affiliate ID into a Moja publisher by itself — you still map publisher ↔ affiliate in the publisher record

Need Help?

Email: support@mojaai.com