Put Current App Offers Beside the Right Experience

A relevant app may also have a useful reason to try it now: a new-member benefit, a trial or a seasonal offer. Blue Jetty Growth publishes that offer beside the experience it applies to, with its eligibility, validity and preferred destination. An AI assistant can draw on those details when answering a potential user's question.

The publisher decides what is available. The assistant decides whether it is relevant. Your app handles redemption and fulfillment.

Make the audience and next step explicit

Suppose someone is looking for a beginner-friendly surf app. A fictional publisher might offer a planning guide to new users who discover the app through an AI assistant. Its packet can state that audience, include a public code, and identify the signup experience where the benefit is available.

Use a specific, accurate statement such as “New users discovering this app through an AI assistant can use WELCOMEAI.” Public codes can be shared, so this is publisher-declared eligibility, not authenticated proof of how a user arrived. Your app enforces the redemption conditions. An offer does not change Blue Jetty's relevance or evidence assessments.

Publish the offer as a maintained record

Configuration 0.5 connects each offer to a destination and records:

• a stable offer ID, title and description;
• its audience and eligibility when applicable;
• a public redemption code when needed;
• a start time and either an end time or explicit ongoing validity;
• active or inactive publication status;
• an optional reviewed binding between the code and a supported link parameter.

Preview the configuration, have the authorized publisher review the exact public content and destinations, then stage and activate the approved revision. Keep the packet aligned with the terms and behavior in the app. The offers guide contains the exact fields and an example.

Give the user an offer-aware destination

If your app reads an offer code from a link parameter, Growth can supply a ready-to-use URL carrying that code. A configured long AppsFlyer OneLink can bind the code to a reviewed deep_link_sub1 through deep_link_sub10 parameter. Supported native HTTPS links can use an unused app parameter. The app must read the value and implement prepopulation or redemption.

For other MMP providers, supply a completed fixed offer URL. Automatic code insertion is not supported for every provider. Existing parameters, signed links and interactive recipes cannot be overwritten or combined with an offer binding. When prepopulation is unavailable, the assistant can present the code alongside the fixed destination.

Test installed and deferred journeys separately. Actual arrival, redemption and attribution depend on the app and its existing link infrastructure. Follow the device-test guide.

AppsFlyer's Unified Deep Linking workflow explains how the app receives deep-link values and uses them to select the in-app experience. For new users, its deferred callback exposes deep_link_value and deep_link_sub1 through deep_link_sub10; your developer must handle those values in the app.

Its OneLink campaign guide also explains how an additional deep-link value can accompany an experience with a discount.

Core includes fixed publisher-supplied MMP and native URLs, including existing parameters. Growth adds managed offers, supported code binding and lifecycle controls.

Keep campaigns current without rebuilding the app map

Only active offers within their validity window appear in new packets. The start is inclusive and the end exclusive. Expiry or deactivation removes an offer from subsequent reads while retaining saved configuration. An ongoing offer remains eligible until changed or deactivated.

Growth sends a review reminder when an unchanged offer approaches expiry within three days. App owners can add up to five agreed recipients for offer-expiry and iOS release-review alerts. The owner remains a recipient; additional addresses are blind-copied and receive no account access. Ongoing offers have no expiry reminder.

Previously retrieved copies cannot be recalled. Keep campaign terms current in the app as well as in Blue Jetty.

Maintain older promotion blurbs deliberately

The legacy metadata field still supports one plain-text blurb of up to 280 characters. It is independent of managed offers and does not expire automatically. Existing users can retain it; new Growth campaigns should use structured offers when they need destinations, eligibility, code binding or lifecycle management.

To remove all promotional context when both paths were used, clear the legacy blurb and activate a managed revision with promotions: []. Deactivating an offer does not clear the separate blurb or delete app inventory.

Measure retrieval and downstream activity separately

Blue Jetty makes your app context available to AI assistants, which decide whether and how to use it. Packet requests show retrieval. Your existing MMP measures eligible downstream activity when users follow your links.

A packet request is not an offer impression or redemption. An absent MMP attribution does not establish that an assistant ignored the context. Start with the structured offers guide to prepare and review your first offer.