Home > Paid Traffic Sources >

---

Tiktok S2S integration (18)

---

Hi guys! Do you know if there's a step by step guide about S2S Tiktok pixel integration using FunnelFlux service? Tried to set it up all day long but still didn't succeed

---

I got it to work but it was literally the most difficult thing I've ever done in 3 years of internet marketing lol... seriously took me like 16 hours of trial and error... 5+ re-uploads with things changed each time...

In retrospect I should have just signed up with Funnelflux instead of trying to make it work with my own tracker... I could have paid for years of their service with the time it took to figure it out...



Edit: That's not because its a bad system or something - its wonderful- just because my tracker is so different from Funnelflux so figuring out how to get the settings right was what was tough.. Also, in addition to using it, I also paid $500 to a company to build me a custom one as well - am happy to give you their contact details but again, in retrospect I would have just signed up with Funnelflux and used their system all on its own.

---

Actually, I updated this article today -- https://help.funnelflux.pro/en/artic...ng-conversions

Ping me over in the FF Pro support chat (just lemme know that you're iska29 from STM).

Should be able to get things figured out pretty quickly, and if you have any issues with the TikTok side I'll have full context and access to my logs to figure things out.

---

Any chance you have the API cost tracking like RedTrack does? I'm strongly considering switching from Voluum since it doesn't support S2S nor cost tracking at this time.

---

Can confirm it works without a hitch if you're used to using trackers and tokens and such. Zeno is also patient and kind and loves everybody

And yes, I got it working on Binom

FunnelFlux is rad tho.

---

I actually found a pretty good workaround for S2S TikTok conversions with Voluum. Assuming you've got your main S2S postback URL syntax (something like https://endpoint.tld/api/?tiktokaccount={something}&pixel={something}&ttcli d={something}&event={something}&accesstoken={somet hing}&value={something}...

What you do is make 1 Traffic Source in Voluum for each TikTok pixel, and then in the traffic source postback URL, you'd hardcode your account, pixel, and accesstoken values, while using Voluum tokens like externalid, payout for the ttclid/payout. The with the TikTok event, you hardcode it as whatever you're chosen as your final conversion, eg CompletePayment. You can expand it further if you use Voluum custom conversions by using the Traffic Source Postback URL per Event Type. If you do that you copy the postback URL exactly, except change the value for event for each one. Anytime you make a new pixel, you duplicate the traffic source, changing the Pixel (and account/accesscode if needed) in the URLs, along with adjusting the event names if the offer has a different flow.

It's a bit of a hassle, but once you get used to it you can do it in 3 mins per offer, and it's working flawlessly for me

---

Thanks. Right now I am using 2 networks. One supports adding it to the various pages, so good there. For the other, I use Zeno's postback solution and just edit the pixel # when needed.

But having it all in one would be nice. Particularly cost tracking.

---

We don't have cost sync yet, but it is something I am personally likely to code in the near future.

I started getting my developer hat on and learning JS properly so that I can contribute to FunnelFlux for stuff like this -- where it doesn't need to be particularly high-level, but where I can use Google serverless tech to build scripts to do stuff.

This way I can use my advantage of understanding exactly how the traffic sources, FunnelFlux, networks and AM works in general to quickly build things that get shit done. And I can skip all the explaining to developers how this stuff should work, requirements, what everything means, etc. as I already get 99% of it at a glance.

Aside from the S2S integration with TikTok, FB, Google Ads, MS Ads and Snapchat, my next target after that will be scheduled cost syncing for these as well, and figuring out our enriched FB reporting API to merge reports from FB with our data > ya FB data with accurate conversion data beside it.

---

@iska29, was the pixel recently created (as in, past 48hrs). I found a really weird bug last night where TikTok seem to have broken Access Code generation and API Authentication for new pixels created after sometime in the past day or two. Older pixels work totally fine, and can work with their current Marketing Apps as well as authorize new ones, but new pixels will fail no matter what. It's really weird because TikTok manages authentication on an account basis, yet things now fail for new pixels on accounts where old pixels work/worked perfectly fine.

There's a really easy way to test if this is a TikTok API bug:
1. Go to Assets > Event > Manage under Website Pixel > Click the name of the pixel > Settings
2. Select 'Use another account's TikTok Developer App, and enter the ID for FunnelFlux, 6930258772682080257, or to double check you can try mine too, 7000316839486029825
3. Click Generate Access Token. If your pixel is fine, it will load an access token. If it isn't it will display a message "App has been deleted or app does not exist"

^^^ If you get something like this, then its a TikTok bug and not something you did wrong. Hopefully they fix it soon, as I can confirm it's effecting all my ad accounts across 3 business centers, so I assume it's probably platform wide.

---

@zeno Thanks again for your TikTok tips, will hopefully run some tests soon to post few results here

---

yes i have the same problem. Apparently the problem really was this, thanks a lot mate!

---

I have opened a ticket with TikTok developer support to get some details on this. Really weird to see the above error, and I want to confirm some things with them.

One important one is, if you create an access token then create a pixel afterwards, does the existing access token have permissions to the new pixel? Quite an important consideration... as if the answer is no, you'd need to make a new access token each time you add a new pixel (but thankfully the old one should not stop working).

---

While it was prior to this, I did create a pixel after creating the access token to utilize your postback and it works just fine. So I would say, it should, barring bugs like this.

---

I can't give definitive answers, as TikTok appears to have fixed the bug as of this morning. However, from my past experience, TikTok pixel authentication has been at the account level, so if you authorize any pixel within a TikTok ads account, all other pixels for that account will be authorized, as well as any future newly created pixels on the account as well.

I think it applies to entire business centers as well if my memory serves me correctly, as I recall when I authorized the first account under my agency business center all the other ones auto authorized, but I'm not 100% sure this was the case or not.

Edit: I got a reply to my developer ticket telling me that they are aware of and are working on this issue (it looks to me like its already fixed now)

---

I tried it yesterday myself and it was working without any problems.

The pixel is ready to optimize towards conversions and I will run some tests now

---

I have had some further discussions with them and currently am confirming the following points, which I believe to all be true:

-- Only pixel owners can generate access tokens usable via the events API. This is the main source of permission denied errors. In the future this may change, as TikTok may allow sub-users (access shared to them by the owner) to have permissions to send events via API

-- Using our auth flow URL and the authentication prompt, users generate an advertiser-level access token i.e. for their user ID, which then has access to all their pixels. This is a 1:1 relationship so new pixels added should be covered by the token.

-- Using the auth token generator in a pixel's settings generates a pixel-level access token scoped only to that pixel ID. This also will only work if you are the pixel owner, so technically its basically an advertiser-level token but is restricted to one pixel ID

-- A standard pixel can still use the events API, but can't send on page JS events using basic event syntax (I tested this, and things like ttq.track('SubmitForm') did not show up in the pixel logs, only rule-based events appeared here -- but I did not test conversions via API).


Still getting full clarity on all this, but I think the main issue they need to fix is allow users who are shared pixel access, to have permissions to send events via API. If they can get the pixel code and place it on pages + push events via JS, its nonsensical that they can't do the same via API.

---

In my experience, using an authentication prompt granted access to all ad accounts within an entire business center. It also covered new future pixels (except for that bug where new pixels couldnt authenticate for anything in their first ~24hrs after creation which now seems to be fixed)

I believe you are correct on that. There is one weird thing that was recently introduced that may be causing issues as well. There is one event type that the on page JS events send that cannot be sent by API - the 'deprecated' PageView event. TikTok didn't actually deprecate it at all. Instead they made it so that it gets automatically sent on all visits whenever the standard pixel or developer pixel base code is present. There is no way to send that event by API however. This is a newish change sometime in the last month, and I'm not sure whether running a campaign only S2S has a negative impact or not, but I am testing it currently.

---

Got a response from TikTok essentially confirming points 1-3 above from me. For point 4 they were still confirming with engineers, but its empirically clear from testing anyway.

---

Home > Paid Traffic Sources >