Skip to main content

Travel Leaders Network Integration - in closed beta

How to set up the Travel Leaders Network (TLN) integration, what syncs between Tern and TLN, and how to use the TLN tab on contacts.

Written by Molly Johnson
Updated today

Connect Tern to Travel Leaders Network to keep contact info, marketing preferences, marketing codes, and trip data in sync between the two systems.

What it does

The TLN integration is a two-way sync between Tern and Travel Leaders Network.

From Tern to TLN, we send:

  • Contact info and marketing preferences

  • Marketing codes (vacation type, interests, mailing parameters)

  • Trip and booking data ("travel history")

From TLN to Tern, we pull:

  • New leads created on the TLN side

  • Marketing opt-outs (email or direct mail) made on the TLN side

This lets you manage your contacts in Tern as your source of truth while still using TLN's marketing tools to reach those clients.

Who can use it

Available to agencies that are members of Travel Leaders Network. Only agency owners and administrators can connect the integration. Once connected, all advisors in the agency see the TLN tab on every contact.

Before you start

You need:

  • An active Travel Leaders Network account

  • Contact Travel Leaders Network at [email protected] to obtain your TLN Agency ID.

  • Agency owner or administrator role in Tern

Setting up the integration

  1. Go to Settings, then Integrations in the Agency section.

  2. Find Travel Leaders Network in the list and click Connect.

  3. Follow the on-screen instructions to enter your CRM ID. We verify the CRM ID with TLN immediately. If it's valid, the integration shows as Active. If it's invalid, you'll see an error and a prompt to try again.

You'll know it worked when the integration shows as Active and the TLN tab appears on your contacts.

Mapping TLN agents to agency members

After you connect the integration, map each TLN agent to the matching agency member in Tern. This makes sure bookings sync to TLN with the correct advisor attached.

Only agency owners and administrators can manage agent mappings.

To map agents:

  1. Go to Settings, then Integrations.

  2. Find the Travel Leaders Network integration.

  3. Find the Agent mappings section. You'll see a row for each TLN agent in your agency, with their name and email.

  4. For each TLN agent, select the matching agency member from the "Mapped to" dropdown. Mappings save automatically. To clear a mapping, select the blank option.

Each TLN agent can be mapped to one agency member, and each agency member can be mapped to one TLN agent. Once a member is mapped, they won't appear in other rows' drop-downs.

The list of TLN agents refreshes every time you open this page. If a new agent is added on the TLN side, it will appear the next time you load the page.

When you map a TLN agent to an agency member, Tern pushes that member's existing data to TLN automatically. This includes all contacts owned by that member that are shared with the agency, plus all bookings on those contacts' trips.

The TLN tab on contacts

Once the integration is active, every contact in your agency has a TLN tab. This is where you see what's syncing and manage marketing details for that contact.

The TLN tab has three sections:

  • Sync details Shows the last time this contact synced to TLN. If a contact isn't eligible to sync, this section shows the reason (see Common issues below).

  • Travel Leaders Network preferences (marketing codes) Add marketing codes to a contact so TLN can target them with the right campaigns.

  • Marketing preferences Toggle whether the contact has opted in to:

    • Email marketing

    • Direct mail

Marketing codes are sent to TLN as a complete list each time a sync runs. Removing a code in Tern removes it in TLN.

How travel history syncs

Tern syncs trip data to TLN within about a minute of any change. When you create or update an activity, booking, package, or insurance entry on a synced contact's trip, the change queues immediately and pushes to TLN on the next sync cycle.

This includes activities, bookings, packages, and insurance. For each booking, we send:

  • Supplier (both the activity supplier and the booking supplier)

  • Travel type (e.g., flight, lodging, tour)

  • Destination

  • Start and end dates

  • Trip length

  • Number of passengers

  • Total cost

  • Booking status (planning, booked, or cancelled)

  • Trip ID, so TLN can group related bookings together

The TLN tab includes a Travel history section listing every booking that has synced for this contact, with the trip name, booking name, a link to the booking, and the last sync date.

What syncs from TLN to Tern

Tern pulls updates from TLN on two schedules:

  • New leads: Pulled hourly.

  • Marketing opt-outs: Pulled weekly on Thursdays, after TLN's Wednesday batch run completes.

When something changes on the TLN side, here's what happens in Tern:

  • New lead in TLN: We try to match it to an existing contact using first name, last name, and email. If we find a match, we update that contact. If we don't, we create a new contact in Tern. An entry is added to the contact's activity log: "New lead created from TLN."

  • Email marketing opt-out in TLN: We update the contact's marketing preferences in Tern to match. An entry is added to the activity log: "Email marketing opt-out from TLN."

Common issues

Contact shows "Not synced" in the TLN tab

There are three reasons a contact won't sync:

  • No marketing opt-in. The contact must be opted in to either email marketing, direct mail, or both. Update marketing preferences on the TLN tab to fix this.

  • No valid email address. If the contact is opted in to email marketing, they need a valid email address on file.

  • No valid address. If the contact is opted in to direct mail, they need a complete mailing address: address line 1, city, state, postal code, and country code.

Fix the missing field, and the contact will sync on the next run.

A contact synced before, but now shows as Not synced

This means the contact no longer meets the eligibility rules. Someone likely removed an opt-in or a required field. The contact will be marked as Inactive in TLN until they meet the rules again.

The CRM ID won't connect

Double-check the CRM ID with your TLN account manager. We verify it against TLN at the time of connection, so an invalid ID will be rejected immediately.

Bookings in TLN aren't attributed to the right advisor

Check Agent mappings in the integration settings. The TLN agent needs to be mapped to the matching agency member in Tern. Once you map them, existing contacts and bookings will sync to TLN automatically.

Did this answer your question?