Skip to content

Zapier

Zapier lets you connect AdvocateLoop to thousands of other apps without writing code. You can react to referral events (a new conversion fires a Slack message, adds a row to a sheet, emails an advocate), send events into AdvocateLoop (record a conversion or refund from another system), and look up a customer’s referral coupon to use elsewhere in your flow.

Adding the AdvocateLoop app in Zapier
Open the invite link, then add AdvocateLoop as a trigger or action in your Zap.

Connect your account

The first time you use AdvocateLoop in a Zap, Zapier asks you to connect your account.

  1. When prompted, enter your API Key and Brand ID.
  2. Both come from your dashboard under Admin → Developers — see Find your API Key & Brand ID.
  3. Zapier verifies the credentials and saves the connection for reuse across Zaps.

Once connected, Zapier labels the connection with your brand’s name, so if you manage more than one brand you can tell your connected accounts apart at a glance.

Triggers

Triggers start a Zap when something happens in AdvocateLoop. Use a trigger as the first step of a Zap, then send the event anywhere — Slack, Google Sheets, your CRM, email, and so on.

TriggerFires when
New ConversionA referred purchase is recorded
New ClaimA referred visitor redeems a referral
New RefundA previously recorded purchase is refunded

Each trigger delivers the details of the event — customer email, order and referral information, the associated coupon, and (for new claims and conversions) the order’s line items — ready to map into the next step of your Zap.

Each Zap with an AdvocateLoop trigger appears in your dashboard under Admin → Developers → Webhooks, and is removed when you turn the Zap off.

An example AdvocateLoop Zap
A typical Zap: New Conversion → notify your team.

Actions

Actions let a Zap send data into AdvocateLoop from another app, or look something up. For the full field reference behind each action, see the REST API page — the Zapier actions map to the same events.

ActionWhat it doesAvailability
Track ClaimRecords a claim against a referral codePremier
Track ConversionRecords a conversion (a referred purchase)All plans
Track RefundRecords a refund against a prior conversionAll plans
Find CustomerLooks up a customer’s most recent open claim by email (a search step)All plans

Track Claim

Records that a customer is redeeming a referral. You provide the referral code and customer email (both required); optionally the customer’s name and phone, a coupon code, the visitor ID, and the order’s line items.

AdvocateLoop applies the same referral rules as everywhere else. When the customer doesn’t qualify, the step stops quietly (Zapier shows it as halted, not as an error) with the reason, for example:

  • the customer has no referral visit on record, or it’s past your attribution window
  • the code is unknown, or its advocate is switched off
  • the customer is the advocate, or has already used a referral (when first redemption only is on)
  • an advocate reward is being redeemed with a different email, or the advocate has no reward available yet
  • the customer or advocate is flagged for fraud

The full list of reasons is under Recording a claim. Recording a claim from an external system through Zapier requires a Premier plan.

Track Conversion

Records a referred purchase. You provide:

  • Customer email (required)
  • Order total (required) — everything the customer paid, including tax and shipping, after discounts
  • Tax, Shipping, Discount (required — enter 0 if not applicable)
  • Optionally: an order ID (recommended — it lets refunds match back to this order and prevents duplicates), the order’s line items, any coupon codes applied, and the purchase date/time

A conversion always belongs to an existing claim. If the customer has no prior claim in AdvocateLoop — created by your widget or by a Track Claim step earlier in the Zap — the conversion is acknowledged but not attributed. When unattributed orders exist, the sale appears under Activity → Unattributed rewards, where you can credit the transaction to the right advocate.

Track Refund

Records a refund against a conversion you previously tracked. You provide the order ID, a refund ID, and the refund amount (all required); optionally a refund reason. For a full refund, send the full order total as the amount; for a partial refund, send the partial amount. AdvocateLoop figures out whether the refund is partial or full from the amounts.

If there’s no AdvocateLoop conversion for the order (usually because it wasn’t a referral order), or it’s already fully refunded, the step stops quietly as halted rather than erroring. Sending the same refund ID twice never refunds twice.

Find Customer

Looks up a customer by email and returns their most recent open claim — including the AdvocateLoop coupon code, referral code, advocate ID (advocate_id), claim type, and line items — or nothing if they have no open claim.

This is most useful when your store or payment processor doesn’t pass the referral coupon into Zapier: look the customer up by email, then use the returned coupon code in a later step. It also works as the search half of a search-or-create (Find Customer → if none found, Track Claim).

Rate limits

If a busy Zap goes over your brand’s rate limit (see Rate limits), the step waits and Zapier retries it automatically. Reaching your plan’s monthly API allowance shows as an error until the allowance resets.

Seeing Zapier in your dashboard

Under Admin → Developers, the Zapier card shows Connected while you have a Zap with an AdvocateLoop trigger turned on, or a Zap has used an AdvocateLoop action in the last 30 days. The card shows which: for example “2 Zaps”, “Actions”, or “2 Zaps · actions”.

Turning off a trigger Zap updates the card right away. Zapier doesn’t tell us when an action-only Zap is turned off, so the card stays connected until 30 days after its last action.

Example Zaps

A few ways teams wire AdvocateLoop into their stack:

  • New Conversion → Slack — post to a channel each time a referral converts.
  • New Conversion → Google Sheets — append a row for reporting.
  • New Refund → CRM — flag the customer record when a referred order is refunded.
  • Order paid in your platform → Track Conversion — record conversions from a checkout AdvocateLoop doesn’t directly integrate with.
  • Find Customer → Track Conversion — when your checkout doesn’t forward the coupon, look it up by email first, then record the conversion.
  • Find Customer → (if none) Track Claim — a search-or-create that records a claim only for customers who don’t already have one.
  • Make — the same idea, using Make instead of Zapier
  • REST API — the underlying events and their fields
  • Webhooks — receive events directly, without Zapier