Choosing between Link-Out Advanced or Basic

Integrating with Flow’s Link-Out involves configuring authentication, creating unique URLs for user access, setting up JWT tokens, and (optionally) incorporating a content feed and webhooks.

Importantly, is the use of a content feed. This determines whether the organisation is set-up with Link-Out Advanced (requires a content feed) or Link-Out Basic (no content feed). There are also some differences in the JWT payloads used between the two, hence also the functionalities between them.

Below are the key details that differ the two options:

Feature	Link-Out Basic	Link-Out Advanced
Content Feed	None. Listings and other campaign data are created dynamically as needed.	Required. A content feed is used to automate data synchronization, including listings, agents, and organizational details.
Office Management	Limited to a single office. Automated creation of multiple offices is not supported.	Supports multiple offices, allowing automated creation and management of multiple office locations through the content feed.
Campaign Data Syncing	Manual. Campaign details, listings, and agent information must be created dynamically or entered manually.	Automated. Content feed provides real-time updates to Flow, synchronizing listings, agents, and campaign data continuously.
User Management	Each user session is initiated through unique URLs with JWTs, with fewer pre-configured user data fields.	Content feed pre-populates user details, allowing more fields and automated updates on agents and organizations.
Ideal Use Case	Suitable for smaller or single-office setups where automation is less critical and manual data handling is manageable.	Ideal for larger organizations with multiple offices, frequent updates, and the need for real-time data synchronization.

Below are the differences in the JWT payload between Link-Out Basic and Link-Out Advanced:

Feature	Link-Out Advanced	Link-Out Basic
Product Identifier	propertyExternalId	listingExternalId
Supports Multiple Products/Listings	Single item only	Multiple items possible
AutoCreate Behaviour	Yes: autoCreate = true is required	No, ignore autoCreate

Scenarios for when to use Link-Out Basic

Scenario 1: Small Offices Without a Content Feed An office does not have a Content Feed but wants its agents to publish ads for properties directly from its internal system.

• Each time an agent clicks “Boost” on a product listing, the system sends all the product details in the JWT payload.

• Since Flow does not have this product stored in its database, the autoCreate flag ensures that the property is created before the ad is published.

Scenario 2: One-Off Product Listing Promotions An agent just created a listing in their CRM, but it hasn't yet been included in the Content Feed.

• The agent wants to run an ad immediately.

• Since the listing isn't in Flow yet, the system sends all its details via propertyExternalId, ensuring it is created dynamically before publishing the ad.

Scenarios for when to use Link-Out Advanced

Scenario 1: Large Platforms with a Content Feed An Enterprise portal has thousands of product listings updated daily through a Content Feed.

• When a user wants to boost a product listing, the system simply references the existing listingExternalId rather than sending all listing details.

• Since Flow already has the product listing, no new data entry is required, making the process faster and reducing potential data inconsistencies.

Scenario 2: Running Dynamic Ads for Multiple Listings An enterprise wants to run carousel or catalog ads showcasing multiple products in a single campaign.

• Instead of passing individual product details, the system sends multiple listingExternalId values (e.g., "listingExternalId": "RNR5103,RNR2240").

• The ad dynamically rotates through different product listings, ensuring greater visibility for multiple properties in a single campaign.