Skip to content

Linking IDentifiers to stops

5 min readUpdated Nov 202615 steps

A Podcatcher Classic plays a Stop when the visitor points it at an IDentifier whose code is linked to that Stop. This page covers what is specific to Classic: entering IDentifier codes on a Stop and on the tour start. Building the tour itself works the same as for every site — see Create a tour and The Tour Editor.

Every IDentifier sends its own code. It is printed on the back of the device as four pairs of characters separated by colons, for example EF:FE:1C:AE. Each character is a digit 0–9 or a letter A–F.

If the IDentifier is already mounted and you cannot see the back, let a Podcatcher Classic read the code — see Read the code when you cannot see the back.

The Platform only accepts a complete code in this format. If a character is missing you see IDentifier code is not complete.

  • Tour start codes are unique on your site. An IDentifier that starts a tour in a language can be linked only once on the whole site. Otherwise the Podcatcher Classic would not know which tour or which language to start.
  • Other codes are unique within a tour. An IDentifier for a regular Stop can be used once per tour, but you can link the same IDentifier to a Stop in another tour.
  • An IDentifier is either a start IDentifier or an Object IDentifier, never both.

The Platform warns you when a code is already in use where it is not allowed.

The first Stop of a tour, the Tour start, starts the tour in a language. It needs an IDentifier for each language of the tour, and that IDentifier’s label shows the flag of the language.

  1. In the Tour Editor, open the tour and click the tour start Stop.
  2. Click Stop settings.
  3. Click the tab of a language.
  4. Under IDentifier code (“Enter the IDentifier code that activates the language.”), click Add another IDentifier and enter the code from the back of the IDentifier. Check that its flag matches the language of the tab.
  5. Repeat for every language tab.
  6. Click Save settings.

More than one start point for the same language

Section titled “More than one start point for the same language”

You can link several IDentifiers to the same language. Click Add another IDentifier again in the tab of that language and enter the next code. Each of these codes still counts as a tour start code, so it cannot be used anywhere else on your site.

  1. In the Tour Editor, click the Stop and click Stop settings.
  2. Under IDentifiers (“A Stop can be activated using various IDentifiers. Enter the ones you want to use here.”), choose IDentifier if a type is asked for, and click Add.
  3. Enter the code from the back of the IDentifier.
  4. To link more IDentifiers to the same Stop, click Add another IDentifier.
  5. Click Save settings.

The IDentifiers of a regular Stop are the same for every language. The language tabs on this screen only change the Stop’s title.

To remove a code, click the trash icon next to it.

Some Stops show a section Legacy IDentifiers. These codes were migrated from the old Podcatcher Portal. They still work, but you cannot edit or remove them yourself. Contact helpdesk@guide-id.com if one of them needs to change.

You can also register IDentifiers before you know which Stop they belong to.

  1. In the Platform, go to Hardware → IDentifiers.
  2. Click Add new IDentifier +, enter the code and click Add another IDentifier for each extra code.
  3. Click Save IDentifiers.
  4. Click Link to Tour Stops to link them right away, choosing the tour and then the Stop, or click Close to do it later.

IDentifiers only work when they are linked to a Stop. In the overview you see for each IDentifier its IDentifier code, the Stop(s) it links to, the Language (for start IDentifiers), when it was Last triggered and its Battery status. Use the icons under Actions to link, unlink or delete an IDentifier. Unlinking keeps the IDentifier in the overview so you can link it somewhere else.

New or changed codes only reach the devices after you publish the tour and the devices have synced. See Publishing a tour and Synchronizing Podcatcher Classic.

Was this article helpful?