AI visibility · tracking profiles
AI answer tracking profiles: ask from every market you sell in
AI answer tracking profiles let Skald ask the assistants as a buyer in New York, London or Montréal would, in their language, on your schedule. Up to 10 profiles a site.
AI answer tracking profiles are the saved settings that tell Skald how to ask the AI assistants: from which place, in which language, which questions, which assistants, how often, how many tries a question, and the most it may spend in a day.
30-day free trial · no card · we set it up within one working day · free to self-host
Four markets, one board. Every run starts from 06:00 in the site's time zone.
Sample profiles. "asks" is questions × tries × assistants. Times are in the site's time zone.
[01] what is sent, exactly
An answer asked from nowhere is a guess. See where each one is asked from.
A buyer in Montréal and a buyer in London get different answers to the same question. So a tracking profile tells each assistant where the asker is and which language they read. Here is the request Skald builds for each one, field for field. Part of AI visibility tracking.
Authorization: Bearer •••• the key, never shown
{
"model": "gpt-4.1-mini",
"input": "Which server-log analytics tool suits a small agency?",
"tools": [{
"type": "web_search",
"user_location": {
"type": "approximate",
"city": "New York",
"region": "New York",
"country": "US",
"timezone": "America/New_York"
}
}]
}
The place in the API's location field
The language English: nothing is added
- place Where the asker is. ChatGPT, Perplexity and Claude take it in a location field. Gemini's API has none, so Skald writes "I am in" and the place as the question's last line.
- language Perplexity takes the first part of the code ("fr" from fr-CA). The others get "Answer in fr-CA." as a last line. English adds nothing.
- key Your own API key, the key the AI company gives you to ask its assistant from a program, goes in the header, to that provider only. Nothing about your visitors is in the request.
[02] refused in plain words
A wrong time zone would quietly ask from the wrong place. Skald says no, and why.
Every profile is checked before it is saved. A three-letter country, half a coordinate or a made-up time zone is refused with a sentence that says what to fix. Type below: this form runs the same checks, in the same order, with the same words.
Saved. A new profile, version 1.
{
"name": "Montréal", "city": "Montréal", "region": "Quebec",
"country": "CA", "lat": 45.5, "lon": -73.57,
"timezone": "America/Toronto", "language": "fr-CA",
"frequency": "weekly", "repeats": 3, "cap": 2.0
}
What is stored: spaces folded, the country in capitals, the cap to the cent. The first problem found is the one you are told.
- 10 profiles a site, at most. The eleventh is refused: "A site has at most 10 profiles. Delete one first."
- 50 questions a site, each 3 to 300 characters. A profile can use the site's list or its own.
- 1 to 5 tries a question, so you read "3 of 5 answers named you", never one yes or no.
[03] when it asks
"Weekly" should mean every seven days, even after a pause. Watch the month play out.
Every 15 minutes Skald looks for a profile that is due. It is due from 06:00 in the site's time zone, once its last run is 1, 7 or 30 days old, or when an admin picked Run now. A paused profile is skipped; once resumed, it runs at the next check if it is due.
- 1
- 2
- 3
- 4
- 508:45 first
- 6
- 7
- 8
- 9
- 10
- 11
- 1206:00
- 13
- 14
- 15
- 16
- 17
- 18
- 1906:00
- 20
- 21
- 22
- 23
- 24today
- 25
- 2606:00
- 27
- 28
- 29
- 30
- 31
Weekly: saved on Mon 5 at 08:40, so the first run came at the 08:45 check. Then every 7 days from 06:00. Next: Mon 26 at 06:00.
Sample month. Runs never pile up: while a run is still open, no new one starts. A run stopped by the daily cap goes on the next day.
We help you write the first questions and pick the markets.
[04] nothing erased
Change the questions in March, and February's figures still mean what they meant. Every edit is a new version.
An edit saves a new version. Each run stores the version and the plan it asked with, so last month's figures keep their meaning. Pick an action to see exactly what it writes.
profile 3 · New York · v2 → v3 · saved Sat 24 Oct 14:07
"name": "New York", "frequency": "weekly",- "repeats": 3,+ "repeats": 5, "cap": 2.0
- run 6 Mon 12 · v2
- run 7 Mon 19 · v2
- run 8 Mon 26 · v3
Run 7's figures were counted from 3 tries a question, and they stay that way. Run 8 asks 5 times. The old body is kept in the profile's versions.
profile 3 · New York · pause, then resume · if you had paused 10–18 Oct
- "paused": [],+ "paused": [["2026-10-10T22:04Z", null]], … resumed … + "paused": [["2026-10-10T22:04Z", "2026-10-18T23:52Z"]],
- ran Mon 5
- skipped Mon 12
- ran Sun 18 · 20:00
- next Sun 25
A pause is a from and to pair, kept forever. You can always see when a profile was not asking, so a gap in the trend has a reason beside it.
new profile 4 · from profile 3 · v1
+ "name": "New York (copy)", + "copied_from": 3, "questions": [ the same 5 ], "providers": [ the same 4 ]
- no runs yet
Copy New York, change the city to Chicago, save. Same questions, new market, its own history from day one.
profile 3 · New York · leaves the list
+ "removed_at": "2026-10-24T18:07Z", runs 1 to 7: kept answers: kept until 400 days pass
- run 7 Mon 19 · kept
- no more runs
Delete stops the asking. It does not take away what was already asked: the trend and the answers stay until the site's days kept (400 by default) pass.
profile 3 · New York · Run now
+ "run_requested_at": "2026-10-24T18:07Z", at the 14:15 check: + run 8 · why "requested" · version 3- "run_requested_at": "2026-10-24T18:07Z",+ "run_requested_at": null,
- run 8 Sat 24 · 14:15
No wait for 06:00. The run is marked "requested", so you can tell it from the scheduled ones.
Sample records. Times in the records are UTC; the run times are the site's (New York). Every change here is also written to the audit log.
[05] who can change it
The whole team should see the answers. Only a few should change what is asked.
Every member of a site reads the answers. Admins and owners change the questions and the profiles. The API keys, which spend money on every site, are for install admins only. Pick a role and try each action.
- Read the answersAI & bots › AI answers
- Save a profileSettings › AI answers
- Set the OpenAI keySettings › Integrations
Pick an action. A viewer reads; the two changes are refused.
What a tracking profile does not do
- A profile is a labelled sample of API answers, a direction over weeks. What everyone in that city sees stays unknown.
- It asks through each assistant's API, which can answer differently from its app.
- Each assistant needs your own API key, and each answer is billed to your account with that provider.
- Gemini's place is a sentence in the question, because its API has no location field. The page says which method each assistant used.
keep reading
More on AI answer tracking profiles
questions
AI answer tracking profiles FAQ
Straight answers, including what Skald does not do.
What is an AI answer tracking profile?
A tracking profile tells Skald how to ask the AI assistants: from which city, region and country, in which language, which questions, which assistants, daily, weekly or monthly, 1 to 5 tries a question, and a daily spending cap. A site can have up to 10.
How does Skald ask from a place?
ChatGPT, Perplexity and Claude take the place in their API's location field. Gemini's API has none, so Skald writes "I am in" and the place into the question. The page names the method beside each assistant: API location, or In question.
How many questions can I track?
Up to 50 questions a site, written the way a customer would ask. A profile can use the site's list or its own, and the same goes for brand terms and competitors.
What happens when I edit a profile?
An edit makes a new version, and each run keeps the version it asked with, so past figures never change under you. A pause is kept as a from and to pair. A deleted profile leaves the list, and its results stay until the days kept pass.
Who can change tracking profiles?
Every member of the site can read the answers. The site's admins and owners, and install admins, can change the lists and profiles, and each change is written to the audit log. API keys are set by install admins and are write-only.
Is anything about my visitors sent to the assistants?
No. Only the questions, the profile's place and its language are sent, to the providers you choose. Do not write anything private into a question.
$ tail -f access.log | skald
See what AI does with your site. Free for 30 days.
No card. We set up hosted Skald for you within one working day, or you self-host it free. Every line of your log, sorted and added up.