Link Attribution
Keep Flutter booking links associated with your partner ID.
Let the SDK build the link
Submit travel context with the quick start. The SDK includes your partner ID (aid) and stored Stay22 session ID (sid22) in the booking experience. Set optional campaign attribution with:
await Stay22.setCampaignId('summer-events');The NotificationClicked event exposes the saved booking URL. Do not replace the issued partner ID with your application name. Test attribution before release.
Send a notification yourself
If your app owns notification delivery instead of using the SDK, a direct booking link can identify that separate flow:
https://www.stay22.com/allez/roam?address=Paris%2C+France&aid=your-partner-id&source=direct&medium=pushnotif_manualKeep the URL on one line. Add checkin and checkout as YYYY-MM-DD, hotelname for a property, or both lat and lng for coordinates. aid determines the partner credited. Use pushnotif_manual for your own notifications; reserve pushnotif and product=mobilesdk for traffic the SDK generates.
Stay22 issues sid22; do not invent one. A self-sent link without it can still credit the partner ID but cannot join the SDK session's notification-to-booking history. When you send the notification yourself, your app owns consent, timing, cancellation and frequency limits.