Simulation
How apps and smart speakers profile you
A simulated phone, a local microphone meter, and official links. Not legal advice. No real advertising id is read.
Understanding the labHow to use it and why you'd want to
Why you'd want to
A simulated tracking choice swaps a scripted SDK list, and a channel class is carried across app, web, speaker, and TV. Microphone samples stay in this browser, and after Accept the page queues lab_interaction.
How to use it
- Change the tracking choice and watch the SDK rows swap.
- Three facts carry forward. Three ids are forgotten.
- A third tap is marked as rage.
- Microphone samples stay in this browser.
Simulation and education. This is not legal advice. Simulated values are labeled. The microphone demo, when you start it, stays in this browser and is not saved or sent by this site.
Simulation. No model call. No new paid service. No real advertising id is read.
1
App tracking
Simulated phone
Allow this app to track your activity?
Simulated id, not this device: SIM-0000
Firebase · screen_view
A screen name. No advertising id in this row.
Meta · ViewContent
An app event name. The simulated device id is omitted when tracking is denied.
Why am I seeing this? The rows are a script. Allow and Deny change whether a simulated advertising id is attached. Apple’s App Tracking Transparency, SKAdNetwork, Android’s Privacy Sandbox, Firebase Analytics, the Meta app events docs, and the Play services advertising id class are linked below. They are not called from this page.
2
Heatmap and replay
0 taps in memory.
Why am I seeing this? Taps stay in memory for this view. A third tap in the same spot is marked rage. Nothing is stored or sent. Reduced motion lists the taps instead of playing them.
3
Smart speakers and voice
Why am I seeing this? Apple’s Siri privacy page says a request may send audio to Apple to process it, and extra audio review is a separate opt-in. Google’s Web & App Activity page is the control for saved activity. Amazon’s Alexa privacy settings page is the account control. This demo does not use cloud speech recognition, because that would send audio off the device.
4
Mic myth and reality
Operating systems surface a mic indicator while an app is using the input. A recommendation that matches a conversation can also come from an account’s search, purchase, or location history. This page does not invent how often that happens.
Why am I seeing this? A granted microphone permission lets that app or page read audio while the permission lasts. This lab does not cite a rate for always-on advertising mics, because it did not measure one. The linked Apple page describes request-time audio, not a statistic about other apps.
5
Cross-device stitching
Carried: channel class: paid social
Forgotten: advertising id; email address; voice recording
Why am I seeing this? This profile is a script: app, then web, then speaker, then TV. The carried fields are categories. The advertising id, email address, and voice recording stay on the forgotten list at every step.
6
Legal snapshot
Why am I seeing this? These are official texts and agency pages, not a summary of what applies to you. Read them. This lab is not legal advice.
WalkthroughHow we built itShowHide
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The apps and voice lab swaps a scripted SDK list when the simulated tracking choice changes, carries a channel class across app, web, speaker, and TV, and keeps microphone samples in this browser. After Accept it queues lab_interaction, and the lab does not call Adobe.
List SDK rows from the choice
sdkEvents always includes a Firebase screen_view and a Meta ViewContent. Allowed adds an MMP install with a simulated advertising id. Denied adds an SKAdNetwork postback with a campaign id only.
Carry three facts and forget three
stitch starts with the channel class. Web, speaker, and TV add the topic. Speaker and TV add a simulated signed-in flag. The advertising id, the email, and the voice recording stay on the forgotten list.
Mark a third tap as rage
addTap keeps the last 24 points in memory. A third tap within eight percent of the previous two is marked rage. The points are not stored.
Keep the microphone here
startMic asks for an audio track, reads time-domain samples, and shows a level. stopMic stops the tracks and closes the audio context. The site does not upload the samples.
Queue the control, not the samples
useLabView queues action view. Allow, deny, the mic button, and a rage tap queue run_demo with labels att-allow, att-deny, mic, and rage-tap. Levels and tap coordinates are not parameters.
From the code
Allow adds a simulated install. Deny adds a postback without a device id.
export function sdkEvents(tracking: "unknown" | "allowed" | "denied"): SimEvent[] {
const base: SimEvent[] = [
{ sdk: "Firebase", name: "screen_view", note: "A screen name. No advertising id in this row." },
{ sdk: "Meta", name: "ViewContent", note: "An app event name. The simulated device id is omitted when tracking is denied." },
]
if (tracking === "allowed") {
return [
...base,
{ sdk: "MMP", name: "install", note: "A simulated advertising id is attached. It is not this browser’s id." },
]
}
if (tracking === "denied") {
return [...base, { sdk: "SKAdNetwork", name: "postback", note: "A campaign id only. No device id." }]
}
return base
}What moves to the next surface, and what stays off the list.
export function stitch(step: StitchStep) {
const carried = ["channel class: paid social"]
const forgotten = ["advertising id", "email address", "voice recording"]
if (step === "web" || step === "speaker" || step === "tv") carried.push("topic: measurement")
if (step === "speaker" || step === "tv") carried.push("account signed in: simulated")
return { carried, forgotten }
}Google and Adobe
Google queues lab_interaction after Accept. Adobe is an example of the same fields.
Queued only after Accept. The page queues lab_interaction with action view and label page. Allow, deny, the microphone button, and a rage tap queue action run_demo with label att-allow, att-deny, mic, or rage-tap. Audio levels and tap coordinates are not parameters. This site does not call gtag('set') or Adobe.
Simplified shape of the object queued after Accept. Register any new parameter as an event-scoped custom dimension. This site does not call gtag('set').
dataLayer.push({
event: "lab_interaction",
lab_id: "apps-and-voice",
action: "run_demo",
label: "att-deny",
})Example implementation. This site does not call Adobe. eVar48, prop48, and event48 are example variable numbers. In Launch, a data element reads the value and a rule sends it when the value changes. In the report suite, enable eVar48 with Most Recent allocation and expire it on the hit. A processing rule is unnecessary if the data element maps straight to that eVar.
Example alloy payload. _example is a placeholder schema, not a real tenant.
alloy("sendEvent", {
xdm: {
eventType: "web.webinteraction.linkClicks",
_example: {
trackingChoice: "denied",
},
},
})Example hit. eVar48 is hit-scoped in this example. prop48 dies at the same hit.
s.eVar48 = "denied"
s.prop48 = "denied"
s.events = "event48"
s.linkTrackVars = "eVar48,prop48,events"
s.linkTrackEvents = "event48"
s.tl(true, "o", "lab_interaction")Translation
Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Tracking choice
GA4. label att-allow or att-deny on lab_interaction when action is run_demo.
Adobe. Example eVar48, expire on the hit.
Scope. Event. A user property would keep a simulated deny onto later pages.
SDK row
GA4. Not sent. screen_view, ViewContent, install, and postback are labels in the script.
Adobe. Example prop48 on the hit.
Scope. Hit, if you tracked one row. The row is not a visit property.
Carried channel
GA4. Not sent. stitch returns the channel class in the carried list.
Adobe. Example eVar48 if you sent the channel class. This event's label is the control.
Scope. Hit. The stitch step is a view state, not a user property.
Microphone level
GA4. Not sent. The level stays in component state.
Adobe. Example: do not write the level into prop48.
Scope. Not an event and not a user property. The samples are not stored.
Recommended next
Why these picksReading path transitions…