# Links Added After Page Load > How AutoTag handles affiliate links that appear after the page loads, how to test them, and what to do when the Click ID is missing. [AutoTag](/docs/autotag) works on the links that are in your page. A link the visitor cannot see yet is still in the page — but a link that does not exist yet is not. That distinction decides whether your offer button carries the Click ID. It matters most on VSL pages, where the buy button appears partway through the video, and on any page where a script builds the link. ## Hidden Is Not the Same as Added Later | Your link is… | Example | Tagged? | |---------------|---------|---------| | In the page, hidden with CSS | Offer button with `display: none`, revealed at 12:00 in the video | Yes — AutoTag treats it like any other link | | In the page, below the fold or inside a collapsed section | Link in an accordion, FAQ, or tab the visitor has not opened | Yes | | Added to the page by a script, after load | Button the video player inserts when the video ends | Verify — depends on how the script inserts it | | Built by a JavaScript framework after data loads | Product list rendered by React or Vue once the API responds | Verify — see [Single Page Tracking](/docs/single-page-tracking) | | Inside a modal that a script builds on click | "Get the offer" popup constructed when the visitor clicks | Verify | | Rendered inside the video player's own iframe | CTA button drawn by an embedded player such as VTurb or converteai | **Never** — see below | | Not a link at all | A `button` element that redirects with JavaScript | No — AutoTag needs a standard `a` element | The first two cases need nothing from you. Revealing a hidden link changes nothing about its `href` — AutoTag already wrote the Click ID into it. The middle cases are worth checking rather than assuming. Video platforms and page builders each insert elements differently, and the result varies. The iframe case is different from all of them, and it is the one to rule out first. ## Check the Iframe First Some embedded video players draw the CTA button **inside their own iframe** rather than in your page. AutoTag runs in your page's document and cannot reach inside an iframe, so a button rendered there is never tagged — no matter how long you wait or how the reveal is timed. The button could be there from the first millisecond and still receive nothing. This matters because it looks identical to a timing problem, but nothing about timing, the Tracking Tag, or your integration settings will fix it. **How to tell in one step:** put a plain HTML link to the same destination somewhere else on the page, outside the player, and load the page. If that link gets a Click ID and the player's button does not, the button is inside the iframe. Stop checking your postback URL, your link format, and your checkout platform — none of them are involved. ### Fix: put the Click ID on the page URL Most embedded players build their button URL from the query parameters on the page that hosts them. Put the Click ID there and the player carries it through. Use the [`atclidToUrl`](/docs/append-click-id-to-url) command, with the parameter name your destination expects — `cid` for a Digistore24 checkout, for example, rather than the default `_atid`: ```javascript ``` **This has to go on the page hosting the player** The player reads the URL of the page it is embedded in. Adding `atclidToUrl` to an earlier page in the funnel does nothing — the value has to be on the URL of the page carrying the video. **AutoScan showing nothing is not the same as tracking failing** [AutoScan](/docs/autoscan) reads your page's initial source, so it cannot see links that only exist once a script has run. A page reporting **No elements found** may still track perfectly, because the Tracking Tag runs live in the visitor's browser. Assign the integration manually in AutoScan, then verify on the live page — the live page is the answer that counts. ## Check Your Link in 30 Seconds Open your landing page in a normal browser window. If you have been editing the page, use an incognito or guest window so you are not looking at a cached version. Play the video, open the popup, scroll — whatever the visitor does to make the offer button show up. Right-click the button and choose **Copy link address**. Paste it into a text editor. The URL should contain your network's SubID parameter with a real value — `tid` or `vtid` for ClickBank, `subId1` for Impact, `sid` for CJ, `atclid` for your own domains. The parameter list for every network is in [Tracking Group ID](/docs/tgid). A URL with no parameter, an empty parameter, or a literal `--CLICK-ID--` still in it means the link was not tagged. **Testing a long VSL without watching the whole video** Duplicate the page, keep the same button, and swap in a video that is a few seconds long. The button reveals almost immediately and behaves identically for tracking purposes. Waiting out a 20-minute reveal to test one link is not a good use of your afternoon. ## Fixes, Best First ### Option 1 — Put the link in the page and hide it with CSS Instead of having a script create the button when the video ends, put the button in the page from the start and reveal it. ```html ``` Your script then only changes the visibility, never the link itself: ```javascript document.getElementById('offer-cta').style.display = 'block'; ``` This is the most reliable option because it removes the timing question entirely. AutoTag tags the link at page load, and the reveal is purely cosmetic. Most video players and page builders support this — look for a "show existing element" option rather than "insert HTML". ### Option 2 — Use the `--CLICK-ID--` token If the link must be written by a script, include the token in the URL your script inserts. The Tracking Tag replaces it with the real Click ID: ```html Get Instant Access ``` Replace `sub1` with your network's parameter. Verify the result with the copy-link test above — if the token is still literally in the URL after the link appears, the script inserted the link after the replacement had already run. Use option 3 instead. ### Option 3 — Build the URL with the Click ID yourself When your script fully controls the link, read the Click ID directly and write it into the URL. Wrap the call in the AnyTrack callback so it runs only once the Tracking Tag has finished loading: ```javascript AnyTrack(function() { var atclid = AnyTrack('atclid'); var offerUrl = 'https://offer.com/product?sub1=' + atclid; // Use offerUrl when you create or reveal the button document.getElementById('offer-cta').href = offerUrl; }); ``` The callback matters. Calling `AnyTrack('atclid')` before the tag has loaded returns nothing, and you end up building a URL with an empty parameter — which looks tagged but attributes nothing. **A button is not a link** If your CTA is a `button` element that navigates with JavaScript, none of these options apply until you give AutoTag something to work with. Either convert it to a standard `a` element, or build the destination URL with option 3 before redirecting. ## The Click ID Is There but Conversions Still Are Not Attributed If the copied URL contains a valid Click ID, tagging is working and the problem is further down the chain. The usual cause is something between the click and the offer rebuilding the URL: a click tracker, a link shortener, or a redirect script that constructs the destination from a hardcoded value and drops everything AutoTag added. The tell is that a page *without* that redirect attributes correctly while this one does not — which points at a script on this page, not at your account settings. To confirm, open your browser's network tab, click the button, and follow the redirect chain hop by hop until the parameter disappears. Every redirect in the path has to pass the full query string through. The full sequence is documented in [Affiliate Click ID Journey](/docs/affiliate-click-id-journey). ***