🤝 Referly Affiliates And Referrals

Referly is a Connect Pack connection for your Referly affiliate program, and it works both ways. As a source it reacts to everything that happens in your program. As a destination it can create and manage affiliates and record referrals and sales.

What you need from Referly:

Referly's API and webhooks are part of its Business plan, or Agency.

1. In your Referly program open Settings, then Advanced, then API Keys. Click Generate New Key and paste the key in API Key on the Referly card.
2. Still under Advanced, open Webhooks and click New Endpoint. Paste the Webhook URL shown on the Referly card, tick all fifteen events and click Create.
3. Open the new endpoint with View Details, reveal the Signing Secret, which starts with whsec_, and paste it in Webhook Signing Secret on the card.
4. Set Your Referly program currency, then click Connect.

WP Sync checks the signature on every event, so only genuine Referly events are acted on.

Checking the connection:

On the endpoint's Testing tab in Referly, click Send Test Event, then click Test Connection in WP Sync. Referly's test events contain made up sample people, so WP Sync confirms they arrived but never runs a sync for them.

Triggers you can pick as a source:

• Affiliate approved. Fires once per affiliate, whether your program approves people automatically or you approve them by hand. Later edits, repeat notifications and retries never fire it again, so a welcome sequence is never restarted. Referly does not always send an update for a hand approval, so WP Sync also checks with Referly every few minutes about anyone still waiting for approval.
• Someone signs up, an application is waiting, an application is declined, an affiliate is deactivated, banned, made active again, or deleted.
• Affiliate details change, such as their profile, commission plan, tier or links.
• An affiliate makes their first sale, earns a commission, or has a commission added to a payout. These send the affiliate.
• A new referred customer, a change to one, or one being deleted. These send the customer.
• A referred customer buys, a sale changes, or a sale is refunded, disputed or removed. These send the customer with the amount, order ID, product and commission.
• A promo code is issued, edited or deleted. These send the affiliate who owns the code.
• A coupon is created, changed or deleted. A coupon has no person attached, so use these with Google Sheets, Slack or a webhook.

Example: approved affiliates onto your email list:

1. Click Create Bridge and pick Referly as the source.
2. In Trigger, choose Affiliate approved.
3. Add your email app and its affiliates list as the destination.
4. Click Create Bridge.

To take people off again, build a second bridge on Affiliate deleted, or deactivated or banned, with the Unsubscribe action on the same list.

Affiliates you already have:

When you connect, WP Sync reads your existing affiliates once, so somebody who was already an affiliate is never mistaken for a new approval. To add them to your list, click Backfill on the approved bridge. Backfill also works for the sign up, pending, referred customer and sale triggers.

Referly as a destination:

Pick the action on the destination step. These are the choices.

• create an affiliate, approved or waiting for approval,
• update an affiliate's name, commission rate or links,
• approve an affiliate or set them back to pending,
• give an affiliate an extra referral link,
• issue a promo code from one of your coupons,
• record a referred customer or a sale,
• mark a sale refunded,
• delete a referred customer or an affiliate.

Deleting an affiliate in Referly also removes their links, referrals, sales and commissions there, so keep that action for clean up bridges.

Recording sales:

A Record a sale step takes the amount and order ID from the source, so any checkout WP Sync reads can report sales to Referly. Referly credits the affiliate who referred that customer, and the order ID means a sale is only counted once. If the buyer was not referred, nothing is recorded and the step still counts as done. For a checkout that Referly's own integration already tracks, such as its Stripe app, let that integration report the sale.

Currency:

Referly reports amounts without a currency, so set your program's currency on the card. WP Sync adds it to sale events, which helps Meta Conversions and Google Sheets.

Example: make every buyer an affiliate:

Some programs invite every customer to promote. Build a bridge with your checkout, such as Stripe, as the source, and Referly as the destination with the action to create an affiliate waiting for approval. Each buyer arrives in Referly ready for you to approve, and the Affiliate approved bridge then welcomes them to your partner list.

Example: report sales from your checkout:

Build a bridge with your checkout as the source and Referly with Record a sale. Referly credits whichever affiliate referred the buyer. Add a Google Sheets destination to the same bridge for a running record of every sale.

Example: tell the team about first sales:

A bridge on An affiliate makes their first sale, with a Slack destination, posts a message the moment a partner earns their first commission.

Reading Referly rows:

Affiliate triggers send the affiliate as the contact. Customer and sale triggers send the referred customer. Sale rows carry the amount, order ID, product and commission, which you can use as tokens, such as a tag Referred by {affiliate}, when the field is present.

Keeping Referly and your list in step:

• Affiliate approved: add to the partner list.
• Affiliate deactivated, banned or deleted: Unsubscribe from the partner list.
• Affiliate made active again: add back to the partner list.

Three small bridges keep your partner list exactly matching your program.

Choosing the trigger in the builder:

After you pick Referly as the source app, the builder shows a Trigger box listing every event above. Pick one, then the list box underneath, and continue to the destination as usual. Build one bridge per trigger you care about, so each event has its own clear follow up.

Testing a Referly bridge:

Referly's own test events never run a sync, so test with a real but harmless change. For example, approve a test affiliate made with your own address, then open History on the Affiliate approved bridge.

Tips:

• Pair Affiliate approved with a welcome sequence for new partners.
• Send sale events to a Google Sheet for a simple running record.