Answers
Making your tracking survive Safari
Check Settings → Tracking → How long your cookie lives. If it says 400 DAYS, close this tab and go enjoy your day. If it says 7 DAYS ON SAFARI, read on, it is worth about twenty minutes of somebody’s time to fix.
What is actually going on
When someone clicks your ad, we store which ad it was in a cookie on their browser. Safari deletes that cookie after seven days if the tracking is served from a different host than your website, which is exactly what a t.yoursite.com subdomain is, because it answers from our servers rather than yours. Safari is not being difficult for the sake of it; that pattern is what actual trackers use to follow people around, and you are getting caught in the net.
The damage is quiet, which is the worst kind. Someone clicks your Google ad on Monday, thinks about it for two weeks, comes back and fills out your form, and arrives as a total stranger. That sale shows up in your unattributed line and the campaign that earned it gets no credit. Chrome and Firefox visitors are fine. Safari, and every browser on an iPhone, are not.
The fix: serve tracking from your own site
Instead of pointing visitors at t.yoursite.com, your site forwards requests from yoursite.com/vt/ to us behind the scenes. The visitor’s browser only ever talks to your domain, so there is nothing for Safari to object to, and the cookie lives the full 400 days. Nothing about your site changes visually and nothing new gets collected.
WordPress
In your own WordPress admin go to Plugins, then Add New, search for MyVitalAssistant, and click Install then Activate. It is in the official WordPress plugin directory, so there is no file to download from us and nothing to upload, and updates arrive the same way they do for every other plugin you run.
Then open its settings and enter the email address you sign in to MyVitalAssistant with. It looks up your account and shows your business name back, so you can see at a glance that it worked rather than wondering. Two minutes, no developer, nothing to copy.
The plugin sets up the forwarding and adds the tracking script itself, so delete the script tag you pasted in by hand. While both are there every pageview is counted twice and the cookie is still capped at seven days, which is the worst of both. The plugin looks for a leftover tag once a day and will tell you on its own settings page if it finds one.
Changing your sign in email later does not affect the site. The plugin uses the address once to find your account and remembers the account, not the address.
Not using Keap forms? The plugin captures your forms automatically
The plugin listens for submissions from Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms, Formidable, Elementor, and even Keap’s own Opt-in Forms popups (which create contacts through the Keap API with no attribution at all otherwise), and sends the submitted email plus the visitor’s attribution to us. We write the attribution onto the Keap contact ourselves once your form’s own Keap integration has created it, retrying quietly for up to a week if the contact takes a while to appear. No hidden fields, no field mapping, nothing to wire, and the plugin’s settings page shows an activity log of every capture so you can watch it work. Not on WordPress? Hidden attribution fields still work on any form whose Keap bridge maps them through; email us and we will walk you through it.
“Another plugin? Is that safe?”
Fair question, and if you have ever cleaned up a hacked WordPress site, an earned one. Start with the part that is not our word for it: this plugin is listed in the official WordPress plugin directory, at wordpress.org/plugins/myvitalassistant. Getting in means the WordPress plugins team read the code themselves and approved it before it was published, and staying there means every update reaches your site through the same channel WordPress already uses for everything else on it.
The rest is what it actually does, and you are welcome to read that too. Plugins get sites in trouble when they store what strangers send them, keep their own database tables, or leave a forgotten upload form lying around. This one does none of that. The public part is a relay: it takes the tracking request a visitor’s browser was already making, hands it to our servers, and passes the answer back. When one of your forms accepts a submission, it also sends the submitted email and the visitor’s attribution cookie to that same collector, so the ad gets credited. The only thing it keeps on your site is its own small activity log, the last 100 captures, in a standard WordPress option so you can watch it work. No database tables, no uploads, nothing executed, and the settings page is only reachable by your site’s administrators. Keeping your PHP version current is still smart hygiene, but that is true with or without us.
Your site is behind Cloudflare
Add a Worker route for yoursite.com/vt/*. We will send you the ten lines.
Nginx, Apache, Netlify, Vercel
A short block in your config that forwards /vt/. Whoever manages your hosting will recognise it instantly, email us and we will send the exact snippet for your setup.
Squarespace, Wix, Shopify, Keap landing pages
These do not let you forward a path, so this fix is not available. You stay on the subdomain install and Safari visitors get seven days. We would rather tell you that plainly than let you assume otherwise, and if most of your traffic is desktop Google Ads, the practical damage is small.
Do I have to do this?
No. Everything works either way; the question is only how long a Safari visitor stays recognisable. If you sell something people decide on the same day, seven days is plenty. If your customers think it over for a few weeks, most service businesses, this is the difference between your ad spend looking worthless and looking like it works.