> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pocketshop.at/llms.txt
> Use this file to discover all available pages before exploring further.
# Schedule and Target App Content with Content Filtering
> Schedule content with start/end dates, target specific customer segments, and manage multi-brand visibility using Pocketshop's content filtering tools.
Content filtering gives you precise control over every piece of content you publish in your app. Rather than managing visibility manually, you can schedule campaigns in advance, restrict content to specific customer groups, and — if you operate multiple brands or franchise locations — decide exactly which app each piece of content appears in. The result is a more relevant experience for every customer and less administrative overhead for your team.
## Availability Controls
Use the availability settings to define when content is displayed and whether it is currently active in your app.
| Field | Description | Example |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| **Available from** | Start date and time for content display. Content remains hidden until this moment is reached. | `01.06.2025 09:00` — launches a summer campaign on the first day of June |
| **Available until** | End date and time for content display. Content auto-deactivates once this moment passes. | `30.06.2025 23:59` — automatically retires the campaign at end of month |
| **Active** | Technical on/off switch. Inactive content is never shown, even if the date window is valid. Set a piece of content inactive to pause it without deleting it. | Toggle off to draft content without publishing it yet |
| **Visible** | Controls whether content appears in the app by default. Invisible content can still be accessed via a direct link, making it ideal for exclusive or gated actions. | Set invisible to hide a coupon page that only push-notification recipients can reach |
Always test new content with an internal employee segment before making it visible to customers. This lets you verify links, images, and reward logic without exposing unfinished content to your audience.
## Segment Targeting
Segment targeting lets you restrict content so that only users belonging to one or more selected segments can see it. Everyone outside those segments sees nothing — the content simply does not appear in their app.
Assign one or more segments in the **Segment** field of any content item. Content with no segment assigned is visible to all users by default.
| Segment example | Content use case |
| -------------------------------------- | ----------------------------------------------------------------- |
| Loyal customers (high visit frequency) | Early access to a new product before the general launch |
| Inactive users (no visit in 90+ days) | A reactivation offer with a special discount |
| Employees | Internal news posts, team announcements, or staff-only promotions |
| VIP programme members | Exclusive events, priority booking, or premium rewards |
Segment targeting works across all content types — news posts, events, coupons, and pages — so you can build personalised journeys without creating duplicate content.
## Multi-App and Multi-Brand Control (Client IDs)
If you operate more than one brand or run a franchise network, Pocketshop supports multiple apps from a single backend. **Client IDs** determine which app (brand) a piece of content appears in, while segments continue to define which users within that app see it.
Think of it this way:
* **ClientID** = the app or brand
* **Segment** = the user group within that app
You can therefore target content at **App A → Segment X** and simultaneously at **App B → Segment Y** from one content item, without duplicating records. This is particularly useful for:
* **Franchise networks** where individual locations run their own branded apps but share a content library
* **Multi-brand retailers** that operate distinct apps for different product lines
* **Holding companies** managing several separate customer-facing apps
Leave the Client ID field empty to make content visible across all apps in your account.
## Scheduling a Time-Limited Campaign
Navigate to the relevant module (News, Events, Coupons, etc.) and open the item you want to schedule, or create a new one.
Ensure the **Active** switch is enabled. An inactive item will not display even if the date window is valid.
In the **Available from** field, set the exact date and time you want the content to become visible. Use this for planned launches — the content will not appear in the app until this moment.
In the **Available until** field, set the expiry date and time. Once this moment passes, the content automatically stops appearing without any manual action on your part.
If this campaign targets a specific group, select the appropriate segment(s). Leave blank to reach all users.
Save the item. Confirm the scheduling summary reflects the correct window, then optionally preview with an internal test segment before the campaign goes live.
## Best Practices
Set **Available from** and **Available until** whenever you know a campaign has a defined lifespan — seasonal promotions, flash sales, or event tie-ins. This removes the need to manually deactivate content at midnight or over a weekend, and prevents expired offers from lingering in the app.
Set a piece of content to **Visible: off** and share its direct link only via a push notification or email to a specific segment. Customers who receive the link can access the content; everyone else cannot discover it through normal browsing. This is ideal for loyalty rewards, surprise offers, or gated early-access campaigns.
When you manage multiple apps, resist the temptation to create separate content records for each brand. Instead, create one record and assign the relevant Client IDs. This keeps your content library clean, reduces maintenance overhead, and ensures updates propagate correctly across all brands simultaneously.
Maintain a dedicated segment (e.g. "Internal – QA") containing only staff accounts. Before making any new content public, assign it temporarily to this segment and verify that every element — images, links, reward logic, scheduling — works as intended. Switch to the real audience segment only once you are satisfied.