https (ssl) tracking pixels in non-hosted trackers

[CostPerKill]

Hi,

I'm preparing to work with a CPA advertiser who:

- can't use postbacks, only pixels
- needs https pixels, since the conversion pages are https
- the pixels will be placed using Google Tag Manager, so I need my own domain for tracking, or else they'll likely be tagged as malware

I normally use non-hosted trackers such as AdsBridge. They let you use your own tracking domains for redirects, postbacks and pixels, but I don't understand how to make them work as https. I think AdsBridge would have to host my SSL certificate too, correct? Or is there another way to "inject" the SSL certificate into the process?

 

[Stephen ThriveTracker]

Hi there,

With Thrive, we can configure/install SSL on your cloud installation so you can use https links and pixels pretty easily.

Please contact us from our site and mention this thread, and we'll make it work for your requirements!

 

[trackingdesk]

Hi,

I'm preparing to work with a CPA advertiser who:

- can't use postbacks, only pixels
- needs https pixels, since the conversion pages are https
- the pixels will be placed using Google Tag Manager, so I need my own domain for tracking, or else they'll likely be tagged as malware

I normally use non-hosted trackers such as AdsBridge. They let you use your own tracking domains for redirects, postbacks and pixels, but I don't understand how to make them work as https. I think AdsBridge would have to host my SSL certificate too, correct? Or is there another way to "inject" the SSL certificate into the process?

You are totally right. You would have to buy a ssl, and delegate it to your tracking provider.
Our image pixel, plays well with google tag manager. Many users use it, so you might want to give it a try.

 

[MxyzptlkFishStix]

You can get certs from Let's Encrypt - Free SSL/TLS Certificates.

 

[Alex AdsBridge]

Hi,

I'm preparing to work with a CPA advertiser who:

- can't use postbacks, only pixels
- needs https pixels, since the conversion pages are https
- the pixels will be placed using Google Tag Manager, so I need my own domain for tracking, or else they'll likely be tagged as malware

I normally use non-hosted trackers such as AdsBridge. They let you use your own tracking domains for redirects, postbacks and pixels, but I don't understand how to make them work as https. I think AdsBridge would have to host my SSL certificate too, correct? Or is there another way to "inject" the SSL certificate into the process?

Hey, @CostPerKill if you have a domain https, simply add it to our system as a redirect domain with http, but pixel as - https.

Have to work well.

 

[CostPerKill]

That's where I'm confused. To make https work correctly, the server that handles the pixel should host the SSL certificate as well. I don't think there's a way to host the certificate on my server if the domain is delegated by CNAME to AdsBridge. AdsBridge would have to host the SSL certificate for me.

@Alex: can you comment on this please?

You are totally right. You would have to buy a ssl, and delegate it to your tracking provider.
Our image pixel, plays well with google tag manager. Many users use it, so you might want to give it a try.

Thanks Laurent. Does TrackingDesk support https for custom domains? I fear that your pixels might be playing well for now, but sooner or later someone using your tracking domains will trigger Google's detectors and then I'm screwed (unless you keep adding new tracking domains ad infinitum, which doesn't sound very practical).

You can get certs from Let's Encrypt - Free SSL/TLS Certificates.

Great resource, doesn't solve my technical challenge though. :/

 

[Alex AdsBridge]

That's where I'm confused. To make https work correctly, the server that handles the pixel should host the SSL certificate as well. I don't think there's a way to host the certificate on my server if the domain is delegated by CNAME to AdsBridge. AdsBridge would have to host the SSL certificate for me.

@Alex: can you comment on this please?


Thanks Laurent. Does TrackingDesk support https for custom domains? I fear that your pixels might be playing well for now, but sooner or later someone using your tracking domains will trigger Google's detectors and then I'm screwed (unless you keep adding new tracking domains ad infinitum, which doesn't sound very practical).


Great resource, doesn't solve my technical challenge though. :/

So, as far as I got it...if you have a domain, you have to buy a sertificate for it. Add the domain into our system through CNAME, but you have to keep in mind that we add subdomain, so you needed to buy either SSL wild card that is valid for all subdomains (*.domain.com) or add the domain to our system (but not all domain name registrar allow such settings). You add domain as a redirect to our system, then you can use our pixels and add there https instead of http.
Should work!

 

[CostPerKill]

That's the thing though: when I delegate the domain (or subdomain) via CNAME to you, YOUR sever will be asked to provide the certificate. And you can't do that, can you?

 

[MxyzptlkFishStix]

Is this what you're trying to setup?

trackerdomain.com
cname.trackerdomain.com pointing to cpaadvertiserdomain.com

 

[CostPerKill]

Well, it's the other way around, isn't it.

https://mytrackingdomain.com -> CNAME -> https://trackerdomain.com

As far as I understand, my SSL cert would have to be hosted at https://trackerdomain.com. Unless there's another way that I'm not aware of - that's what I'm trying to find out here!