Connect RedTrack and Koast imports your RedTrack clicks, conversions, revenue and cost for your Meta campaigns every night. Your Agent Tasks can then watch RedTrack numbers, like ROI or profit, and act on them. Turn on the spend push and Koast also sends your live ad spend into RedTrack every hour, so RedTrack's cost, profit and ROI stop depending on cost you copy in by hand.

Before you start

• You need your RedTrack API key.
• You need access to integrations in Koast. Integrations are set per ad account, so connect RedTrack while the right ad account is active.
• RedTrack is on request. If you don't see RedTrack in Settings, message us and we'll turn it on.

Connect RedTrack

1. Open Settings, then RedTrack under Integrations.

2. Select Add API Key.

3. Paste your key into API Key and select Save.

The tab now shows Connected. Under Data Processing Status you can follow the import, for example "Progress: 42% (153/365 days)", and see the range of days available. Below it, Campaign mapping pairs each Koast campaign with its RedTrack campaign. Everyone on the team can see it. Only the organization owner and admins can change a pairing or the spend push. See The mapping table.

See RedTrack in Ads Manager

1. Open Ads Manager with the ad account selected.

2. Turn on Show RedTrack Data above the grid.

Eleven RedTrack columns appear: Clicks, CPC, Conversions, CVR, Revenue, AOV, Cost, CPA, Profit, ROAS and ROI. Turn the toggle off and they're hidden again. If RedTrack isn't connected yet, the toggle offers to connect it.

This toggle is still rolling out. If you don't see Show RedTrack Data above the grid, message us and we'll turn it on for your organization.

Use RedTrack in Agent Tasks

In a Monitor rule, pick a RedTrack metric as the thing to watch. The RedTrack metrics are Clicks, Spend, Conversions, Revenue, CPA, ROI, ROAS, CVR, RPC, CPC, AOV, Profit and Profit Margin. For example: pause a campaign when its RedTrack ROI drops below 20% over the last 3 days.

If Koast can't work out a RedTrack number for a campaign, the rule skips it rather than treating it as zero. See Monitor rules reference.

Push spend to RedTrack

Koast reads each campaign's spend live from the ad platform and writes it into the RedTrack campaign it's mapped to. It's off until you turn it on, and it's set per brand.

Turn it on

1. Open Settings, then RedTrack, with the brand you want selected. Only the organization owner and admins can change it.

2. Turn on Push spend to RedTrack.

3. Check the mapping table below the toggle, and pick a RedTrack campaign for any row that has none.

The mapping table

Each row pairs a Koast campaign with the RedTrack campaign its spend goes to.

• Matched automatically. Koast finds the pair from your last 14 days of RedTrack clicks, using the campaign ID your tracking links pass in sub3. These rows refresh every hour.
• Not matched. Campaigns with spend today or yesterday that Koast couldn't pair. Pick the RedTrack campaign by hand. A campaign seen under two RedTrack campaigns is listed here too, with both as options, because Koast won't guess.
• Your pick wins. A campaign you mapped by hand is never changed by the automatic match. Clear your pick to hand it back.

Some rows are kept out of the push on purpose, and the table says why:

For a Koast ad account, automatic matching can't find a pair: your tracking links carry Meta's campaign ID, and Koast only knows the Koast ad account's own campaign ID. Map those campaigns by hand. Each one needs a RedTrack campaign of its own.

When it runs

• Today, every hour. Each push sends the campaign's spend from midnight to now, in the ad account's timezone. A later push replaces the earlier figure rather than adding to it.
• Yesterday, once more after the day closes. After 2:00 in the ad account's timezone, Koast sends yesterday's final spend.
• Only campaigns that spent something are pushed.

One request a minute per RedTrack key

RedTrack's cost API takes about one request a minute, so Koast sends at most one request a minute for each RedTrack API key. Each request covers one campaign for one day. That means a pass takes about a minute per campaign: 10 campaigns with spend take about 10 minutes, and 50 take about 50 minutes. Shortly after 2:00, when yesterday's final push runs too, a pass takes about twice as long.

Brands that use the same RedTrack key share that one queue. Brands with different keys run side by side. If a pass is still running when the next hour starts, Koast lets it finish instead of starting a second one.

When something goes wrong

• The RedTrack key changes. When anyone connects a different RedTrack key to the brand, Koast turns the push off, so spend never goes to a RedTrack account nobody checked. The owner or an admin turns it back on. Saving the same key again changes nothing.
• RedTrack rejects your key. The key is wrong or was revoked, or your RedTrack plan doesn't include API access, or the account is in standard mode. Koast turns the push off for that brand and shows RedTrack's error. Fix it in RedTrack, then turn the push back on.
• Any other failure. RedTrack answered with an error or couldn't be reached, or Koast couldn't read the spend from the ad platform. Koast shows the last error and tries again on the next hourly pass, yesterday's final push included.
• Your timezones differ. RedTrack reads the push window in your RedTrack account's timezone, while Koast builds it in the ad account's timezone. If they differ, the hours are shifted by the difference. Set both to the same timezone.

Good to know

• Today fills in overnight. Koast imports RedTrack once a day, at 3:00 UTC, and brings in the day before. So today's numbers are partial or missing until the next nightly run.
• Days follow your RedTrack timezone. RedTrack decides where a day starts using the timezone set on your RedTrack account. If that isn't UTC, a day in Koast can be offset from a day in Meta by your UTC offset.
• Only Meta traffic. Koast keeps traffic whose RedTrack source is facebook, which RedTrack's Meta traffic channel template sets by default. Traffic from your other channels is left out on purpose.
• Your links must pass Meta's IDs. Koast matches RedTrack data to your campaigns by the Meta campaign ID in sub3, the ad set ID in sub2 and the ad ID in sub1. If your tracking link still shows a raw macro such as {{adset.id}}, the ID was never filled in and that traffic can't be matched. See Tracking data looks wrong.
• The import is Meta only. Imported RedTrack data doesn't cover Koast ad accounts. The spend push does, through campaigns you map by hand.

Disconnect RedTrack

In Settings, RedTrack, select Disconnect under "Disconnect integration" and confirm. Koast stops fetching RedTrack data and stops pushing spend, and any Agent Task that uses RedTrack metrics stops working until you reconnect.