01. A developer adds a block of custom tracking code to a page. On the next load the console reports Uncaught SyntaxError: Unexpected end of input, and no Adobe Analytics activity appears at all.
What has happened to that block of code?
a) It ran as far as the fault, so the lines above it took effect and the rest were skipped.
b) Only the malformed statement was skipped, and the browser carried on with the rest of the block.
c) None of it ran, because the browser could not parse the block, so the s.t() call in it was never reached.
d) The block executed, but each Analytics call inside it failed silently because the s object had not been created.
02. A documentation page links to a PDF datasheet hosted on the same site. The team wants each click on that link to be recorded in the Downloads report rather than as a page view or a custom link, and a tracking call has been added to the link's click handler.
Which call reports the click as a download link?
a) s.tl(this,'download','Datasheet PDF'); — the link type is spelled out to make the intent explicit.
b) s.tl(this,'e','Datasheet PDF'); — 'e' is the link type used when the click sends the visitor to another domain.
c) s.tl(this,'o','Datasheet PDF'); — 'o' is the link type used for interactions that stay on the page.
d) s.tl(this,'d','Datasheet PDF'); — 'd' is the link type used for a file download.
03. A page's tracking code assigns s.eVar5 the campaign name taken from the data layer. Reviewing the source, a developer confirms the assignment runs and that the variable holds the right value immediately afterwards. The beacon, however, carries a different value in eVar5 on every page.
Where should the developer look first?
a) At doPlugins(), which AppMeasurement runs while the hit is assembled and therefore after the page's own assignments, so whatever it writes to eVar5 on every hit is what ships.
b) At the expiration and allocation configured for eVar5 in the report suite settings, since a value carried forward from an earlier hit, or from an earlier visit, will replace the one assigned on this hit.
c) At the Adobe Launch data element feeding the assignment, since a data element that resolves after the rule has completed substitutes its own value into the hit.
d) At a processing rule that overwrites eVar5 after collection, since a rule configured to overwrite applies to each hit that carries eVar5 in that report suite.
04. A rule fires on every page view and calls s.t(). Debug logging confirms the rule and its action run, the console shows no JavaScript errors, and breakpoints show the expected values assigned on the s object.
No request to the tracking server appears in the network tab on any page.
Which cause is consistent with every one of those observations?
a) The tracking server value is absent from the configuration, so AppMeasurement raises an error while assembling the request and the hit is dropped.
b) Custom code sets s.abort = true, which AppMeasurement reads after doPlugins() has run and uses to drop the hit before the hit becomes a request.
c) The rule's action calls s.t() where the interaction being tracked requires s.tl(), so the hit is built for the wrong call type and is not sent.
d) A processing rule in the report suite is discarding these hits, so nothing reaches reporting and no entry is recorded in the network tab.
05. A visitor adds two products to the cart in one action. One was found through on-site search and the other by browsing a category, and the SDR requires eVar9 to hold the finding method of the product it belongs to, so that later orders can be credited to the right method per product.
Which approach satisfies the requirement?
a) Assign s.eVar9 inside a doPlugins() function that reads the finding method from the data layer, so that the value is applied to each product as the beacon is built.
b) Set the value once for the whole hit: s.eVar9 = 'search'; before the cart-add call, leaving the products string as 'Gear;Tent;1;249.00,Gear;Stove;1;39.00', so the cart-add event binds it to the products on the hit.
c) Send two separate cart-add hits, one per product, each with its own s.eVar9 value assigned before the call.
d) Set the value inside each product's own merchandising field: s.products = 'Gear;Tent;1;249.00;;eVar9=search,Gear;Stove;1;39.00;;eVar9=browse';
06. An hour after a release, a stakeholder reports that a new success event shows no data. The developer confirms in the browser that the beacon leaves the page, that it carries the event, and that the report suite ID on the request is the production suite.
Which observation would show that the cause lies in collection or configuration rather than in reporting latency?
a) The debugger lists the success event in the request's query string with the value the implementation intends.
b) Other variables from hits sent by the same browser in the same hour are already visible in the report.
c) The image request returns a 1x1 transparent image, which shows that Adobe's collection servers accepted it.
d) The Adobe Launch library carrying the change was built and published to the production environment before the release went out.
07. An operations team runs an internal dashboard outside Adobe Analytics. It has to show the same visit and order figures the Analytics reports show, including figures for the day in progress, and it has to refresh itself several times a day without anyone exporting a file by hand. The team wants the figures Adobe reports, not the individual hits behind them, and it is not sending any data into Adobe Analytics.
Which component of Adobe Analytics serves this requirement?
a) Data Warehouse, which returns processed figures rather than raw hits and can be scheduled, so the dashboard receives a fresh extract without anyone exporting a file.
b) Data Sources, which connects the dashboard's system to the report suite so that figures can move between the two on a schedule.
c) Data Feeds, which deliver the collected hits to storage the team controls on a schedule, leaving the dashboard to add them up however the business defines each figure.
d) The Reporting API, which returns report data programmatically, so the dashboard requests the figures itself each time it refreshes.
08. In a dispute about missing data, a developer argues that the implementation must be sound because every tracking request in the network tab completed successfully and returned the 1x1 transparent image.
What does that response actually establish?
a) That no content blocker interfered with data collection, and therefore that the same request is being sent by visitors' browsers too.
b) That the hit has been processed into the report suite, so a figure still missing must be a fault in the report the stakeholder opened.
c) That Adobe's collection servers accepted the request from this browser, and nothing about what happened to the request after that point.
d) That the report suite ID on the request is a valid one, because a request naming an unknown suite is answered with an error instead of the image.
09. On a retail site eVar12 holds the internal search term. It is set on the search results page view and is configured to persist beyond the hit that sets it. From a results page a visitor clicks an exit link to a partner catalog, which fires:
- s.linkTrackVars = 'eVar5';
- s.tl(this,'e','Partner Catalog');
A stakeholder asks whether eVar12 has to be added to s.linkTrackVars for the exit link to be attributed to the search term.
What should the developer tell them?
a) No, because the persisted value is applied to later hits during reporting, so the exit link is already credited to the search term without being sent again.
b) No, and eVar5 can be dropped from s.linkTrackVars as well, since anything already assigned on the s object travels with the link hit unless it is excluded.
c) Yes, because a variable that is not named in s.linkTrackVars is left off the link hit, and reporting can only credit a value that the hit itself carries.
d) Yes, because persistence only continues across hits of the same type, so a link hit that follows a page view needs the value restated to keep the chain intact.
10. Paid advertisements point at a short vanity URL. That URL serves a small interstitial page which redirects the browser on to the campaign landing page in JavaScript. The landing page is tagged and its page views are collected normally, but in the referring domain report these visits are credited to the vanity host rather than to the advertising networks whose ads were clicked.
The interstitial can pass the address that referred it through to the landing page, where the tracking code can read it. What should the developer do so that each of these hits is credited to the site the visitor actually came from?
a) Capture the original referring address into a conversion variable of its own on the landing hit, and report the advertising networks from that dimension.
b) Read the address the interstitial passed through and assign it to s.referrer on the landing page, before the tracking call assembles the hit.
c) Assign document.referrer to s.referrer on every page view, so the value the browser reports is carried explicitly rather than picked up automatically.
d) Add the vanity host to the report suite's internal URL filters, so that hits referred by it are not counted as arriving from an outside site.