Tag not reading when tapped

Symptom

You tap your phone on the Kitetag and nothing happens — no notification, no browser opening.

Likely causes and fixes

Phone placement is off. The NFC antenna on most phones is near the top-center of the back. Hold the top half of your phone flat against the tag for 1-2 seconds. Do not just touch the corner.

NFC is disabled on the phone. On Android, go to Settings > Connected devices > Connection preferences > NFC and make sure it is turned on. On iPhone 7 and later, NFC is always enabled for tag reading — no setting to change.

Phone case is blocking the signal. Thick cases, metal cases, or cases with built-in card holders can interfere with NFC. Try removing the case and tapping again. If that fixes it, switch to a thinner, non-metallic case.

Phone does not support NFC. Most modern smartphones support NFC, but some budget models do not. Check your phone’s specifications. iPhones from iPhone 7 onward and most Android phones from 2015 onward include NFC.

Tag shows Test Flight instead of my content

Symptom

You tap the tag and see the Test Flight screen showing tag details, instead of your URL redirect, vCard, or other configured action.

Likely causes and fixes

No interaction is configured. Test Flight is the default app for all new Kitetags. You need to create a Kitetag Interaction (KI) on the tag’s group and assign a different app. Go to your Kitetags dashboard, navigate to the tag’s group, and create an interaction.

Tag is in the wrong group. The tag may belong to a group that does not have the interaction you expected. In the dashboard, check which group the tag belongs to. Move it to the correct group if needed.

Wrong data showing after a tap

Symptom

The tag triggers the right app, but the data is incorrect — wrong name on a vCard, wrong URL in a redirect, or missing fields.

Likely causes and fixes

KDS fields have incorrect values. Open the tag in the Kitetags dashboard and check the KDS field values. Edit any fields that are wrong and save.

Tag is in the wrong group. If the tag is assigned to a group with a different data structure, it will display that group’s data. Verify the tag’s group assignment in the dashboard.

Interaction is mapped to the wrong fields. In the interaction configuration, check that each app field is mapped to the correct KDS field. A mismatched mapping can cause the right data to appear in the wrong place.

Webhook not firing

Symptom

You tap a tag that should trigger a webhook, but your endpoint does not receive a request.

Likely causes and fixes

Endpoint URL is incorrect. Double-check the URL in your webhook interaction configuration. Make sure it includes https:// and the correct path. Typos in the URL are the most common cause.

Endpoint is not publicly accessible. The Kitetags platform sends webhooks from its servers, not from your local network. Your endpoint must be reachable from the public internet. If you are developing locally, use a tunneling tool like ngrok to expose your local server, or test with webhook.site first.

Endpoint is returning an error. Check your server logs for incoming requests. If the endpoint is returning a 500 or other error status, the issue is in your server code. See the webhook reference for the expected request format.

Firewall is blocking the request. Make sure your server’s firewall allows incoming POST requests from external IPs on the port your endpoint uses.

Zapier zap not triggering

Symptom

You tap a tag that should trigger a Zapier zap, but nothing happens in Zapier.

Likely causes and fixes

Zap is not published. In your Zapier dashboard, check that the zap is turned on (published). Draft or paused zaps do not run. See the Zapier integration guide for publishing steps.

API key is invalid or expired. If you regenerated your API key in the Kitetags dashboard after connecting to Zapier, the old key no longer works. In Zapier, go to My Apps, find your Kitetags connection, and reconnect with the new key.

Zapier task quota is exhausted. If you have used all your Zapier tasks for the billing period, zaps pause automatically. Check your usage in Zapier under Settings > Usage. See the Zapier cost guide for planning.

Wrong trigger configuration. Make sure the zap’s trigger is set to Tag Tapped and, if you are filtering by group, that the group matches the tag you are tapping.

Tag is frozen

Symptom

You tap the tag and see a page saying the tag is inactive or frozen, instead of your configured response.

Likely cause and fix

Payment issue. Tags enter a frozen state when your Kitetags subscription lapses or a payment fails. Your configuration and data are preserved, but tags stop delivering your configured interactions.

To fix this:

  1. Log in to your Kitetags dashboard.
  2. Go to Account > Billing.
  3. Update your payment method or renew your subscription.
  4. Tags resume normal operation once payment is processed. No reconfiguration needed.

See the FAQ for more details on what happens when a subscription lapses.

Still not working?

If none of the fixes above solve your issue, contact Tagstand support:

When reaching out, include:

  • Your Kitetags account email
  • The tag’s callsign or UID
  • A description of the symptom and what you have already tried
  • Screenshots if possible

Next steps

Last updated 27 Mar 2026, 06:51 +0900 . history