- Home
- Resources
- Integrations
- Optimise
Optimise Zapier integrationAutomate Optimise with Zapier.
The Optimise Zapier integration connects your partner programme to the rest of your stack. Zapier lists 1 trigger, 2 actions and 0 searches for Optimise: follow new conversions, create tracking links and update the status of a conversion.
Verified Trustpilot reviews · AI, automation & growth agency
What the Optimise Zapier integration does for an advertiser
Connecting Optimise to Zapier means a conversion recorded in Optimise can start work in another tool, and other tools can create links or settle conversions in Optimise without anyone logging in. Optimise is a partner platform where advertisers and their partners run long-term programmes. Zapier moves that data in and out on a schedule set by your plan.
Three results advertisers typically build. A conversion log: AdvertiserConversions writes every new conversion into a shared sheet, so finance and the partnership manager read the same list. Links on demand: a new product page or campaign URL in your planning sheet goes through Create Link, and the tracking link is ready to send to partners. Status kept in step with your orders: when your shop or order system decides that a sale stands or was cancelled, Update Conversion passes that status back to Optimise.
Now what Zapier does not do here. The only trigger is a polling one, so Zapier learns about a conversion on its next check, not when it happens; your plan sets that delay. There is no search, so a Zap cannot look up an older conversion or an existing link before acting. And the conversion status you send has to come from the system the Zap started from: Zapier does not work it out for you.
For the wider picture, the Zapier review sets out the platform, and Make vs Zapier covers one alternative.
Zapier vocabulary in one pass
Seven terms run through this page. Each one in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Optimise has one: a new conversion added to your account.
- Action
- What the Zap does once started, the step that writes something. Optimise has two: create a link, update a conversion.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts these.
- Polling vs instant
- Zapier checks a polling trigger on a timer; an instant trigger is reported by its app right away. Optimise's trigger is polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your Optimise account linked to Zapier once, then reused by every Optimise step in every Zap you build.
What an Optimise Zap costs
Optimise is not a premium app, so it runs on the free plan. Zapier bills in tasks, and a task is an action that completed.
- AdvertiserConversionsFree, never counted
- Each Optimise action1 task when it succeeds
- Failed actionNot counted
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, available on the free plan
Watching for new conversions costs nothing, however often Zapier checks. Each successful Create Link or Update Conversion is one task, and each action in another app after the trigger is one more; a failed action is not counted. The free plan builds two-step Zaps only, so AdvertiserConversions feeding one sheet fits. Add a filter to keep only certain conversions, or a second action, and the Zap turns multi-step, which needs a paid plan. The plan also sets how often the trigger is checked.
Connect Optimise to Zapier in three steps
- 01
Open Apps
In Zapier, go to Apps and click + Add connection. In the dialog that opens, type Optimise in the search box and pick the app from the list of results.
- 02
Sign in to Optimise
Click Add connection. A tab opens on Optimise: sign in with the advertiser account whose conversions and tracking links your Zaps will read and change.
- 03
Grant access
Allow Zapier to act on the account. The connection is saved and reused by every Optimise step. If the programme is managed under someone else's account, you need write access to it before you build.
Your first Optimise Zap: a shared conversion log
GoalEvery new conversion lands as a row in the finance sheet, and the partnership manager gets a heads-up.
- 01
Pick the trigger
Build the Zap with Optimise as the starting app and AdvertiserConversions as the event, then select the Optimise connection you just created.
- 02
Test on real conversions
Run the test. Zapier brings back the three most recent conversions of your account, so the mapping is done on real sales rather than an example.
- 03
Add the sheet
Add Google Sheets as the first action, choose the finance sheet, and map each detail of the conversion into the column where the team expects it.
- 04
Add the heads-up
Add a Slack action that posts to the partnerships channel. With two actions the Zap is multi-step, so it needs a paid plan to run.
- 05
Test, then publish
Test the action and check the new row. Click Publish to switch the Zap on. Conversions recorded before that moment stay out of the sheet.
The Optimise trigger on Zapier
1 event starts a Zap when something happens in Optimise. Zapier checks for them at the interval your plan allows.
AdvertiserConversions
Polling triggerIn Zapier“Triggers when new Conversions are added to your account.”
Starts the Zap when new conversions are added to your Optimise account. Each one becomes available to the next steps, ready to be logged, reported or announced without anyone exporting a list. It is the only way an event inside Optimise can set something off on Zapier, so every Zap that reacts to your partner programme starts here.
Optimise actions on Zapier
Optimise gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Link
ActionIn Zapier“Creates a new tracking link”
Turns a page address into a new Optimise tracking link that partners can share, so a fresh landing page is ready for the programme without a trip into Optimise.
Update Conversion
ActionIn Zapier“Updates an existing Conversion”
Changes the status of a conversion that already exists in Optimise, which is how a confirmed or cancelled sale reaches the partner side.
When an Optimise Zap breaks
Zapier attaches no help article to Optimise, so the limits below are Zapier's general ones, plus what the two actions require.
Few of these show up as a red error. They show up as conversions missing from a report, or statuses that never changed. Check the cases below before publishing; the Zapier troubleshooting page covers the general method.
Past conversions are not sent
A Zap only reacts to what happens after it is switched on. Conversions recorded before you published it never start it; moving that history is a separate job.The status comes from the wrong place
Update Conversion needs a Conversion Status taken from the data source your trigger uses. A status typed by hand or taken from another system is the first thing to check.A large batch is held back
When a big batch of conversions arrives at once, after an import or a migration, Zapier's flood protection can hold it back instead of running every step.The same conversion is not sent twice
AdvertiserConversions is a polling trigger, and Zapier remembers what it has already seen, so one conversion does not start the Zap twice.
Need help automating Optimise with Zapier?
A person reads every message.



