> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobyco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Feed

> The in-app content feed - content types, targeting, scheduling and navigation.

The feed is the stream of content a customer sees in the app and in web channels. Marketers author items centrally; your channel asks for the active feed for a customer and renders what comes back.

Each item pairs a piece of media with targeting and scheduling rules, so the same request returns a different feed for different customers.

## Content types

| Type | Contains |
| - | - |
| Image | An image, with an optional navigation action. |
| Video | A video URL plus a thumbnail image. |
| Text | Text only, for announcements. |

<Info>
  Media is uploaded to cloud storage and served over CDN, so you always receive URLs rather than binary content. Videos can be up to **1 GB**, which means you should not assume a feed response is cheap to preload in full.
</Info>

## Feed categories

Every item carries a category. Use it to decide placement and grouping in your UI — the service does not lay the feed out for you.

| Category | Typical content |
| - | - |
| Inspiration | Lifestyle content, recommendations, recipes |
| Purchase | Purchase-triggered and receipt-based content |
| Store News | Store-specific announcements |
| Store Offers | Location-based promotions |
| Store Specials | Limited-time local offers |
| Green News | Sustainability initiatives |
| Good Price | Price promotions |
| Weekly Good Price | Recurring weekly price campaigns |
| Partner Benefit | Third-party partner offers |
| Partner Benefit Banner | Banner-style partner promotions |
| Survey | Feedback and survey invitations |
| Event | In-store events and community activities |
| Special Poll | Engagement polls |

## Targeting

Three targeting modes balance reach against personalisation. The service evaluates them when you request a customer's feed — you never filter client-side.

| Mode | Reaches | Configured with | Use for |
| - | - | - | - |
| **Broadcast** | Every customer, no restrictions | Nothing | Universal announcements, brand messaging |
| **Audience** | Customers in one or more segments | Segments from the [Audience](/integration/loyalty-and-membership/import-audiences-from-your-system) service | Most campaign work |
| **Customer** | Named individuals | A file of customer IDs, with optional personalisation tokens | Account notifications, loyalty milestones, one-to-one offers |

Content can additionally be scoped to chains and stores, so a customer only sees items relevant to the estate they shop.

## Lifecycle

```mermaid theme={"system"}
flowchart LR
    D["Draft"] --> P["Published"]
    P --> A["Active"]
    A --> E["Expired"]
    E --> R["Queryable for reporting"]
```

An item is authored as a draft, validated against the rules for its content type, then published — either immediately or scheduled for a future date. It becomes inactive automatically once its expiration date passes; nobody has to withdraw it by hand. Expired content stays queryable for reporting until it is deleted.

<Warning>
  Unpublishing takes effect **instantly** across all channels. That makes it the tool for pulling a campaign in a hurry — but it also means a cached feed on the client can outlive the content. Re-fetch rather than trusting a long-lived cache.
</Warning>

## Navigation

An item can carry an action that fires when a customer taps it. There are two kinds.

### External URL

Sends the customer to a web page.

| Field | Value |
| - | - |
| `NavigationType` | `External` |
| `ExternalUrl` | Destination, e.g. `https://www.example.com/promotion` |
| `UseWebWrapper` | `true` opens an in-app web view; `false` hands off to the device browser |

Good for landing pages, partner sites, product information and registration forms.

If you set `UseWebWrapper` to `true`, read [Web Content in Mobile App](/integration/app-and-web/web-pages-in-the-lobyco-app) — the constraints there apply to your page.

### Deep link

Sends the customer to a screen inside the app.

| Field | Value |
| - | - |
| `NavigationType` | `DeepLink` |
| `DeepLinkId` | Target screen or feature, e.g. `product-detail` |
| `DeepLinkParameters` | Optional JSON object passed to the destination |
| `DeepLinkUrl` | Generated for you — read-only |

Good for product details, offer redemption, jumping to loyalty points or the shopping list, or triggering an in-app action such as the barcode scanner.

#### How the deep link URL is built

Give the service a `DeepLinkId` and `DeepLinkParameters`, and it generates the full `DeepLinkUrl` for you, following your organisation's deep linking scheme. The result works with both iOS Universal Links and Android App Links.

With `DeepLinkId` of `product-detail` and parameters:

```json theme={"system"}
{
  "productId": "12345",
  "categoryId": "electronics",
  "highlightOffer": true
}
```

the generated URL follows your app's scheme, for example `yourapp://product-detail?productId=12345`.

### Button text

`ButtonText` is the call-to-action label. Leave it empty to hide the button entirely — useful for items that are purely informational. Typical values are "Learn More" or "Shop Now" for external URLs, and "View Details" or "Redeem Offer" for deep links.

## API reference

Endpoint documentation for this service: [Feed](/api-reference/communication/feed).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.