> ## 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.

# Create App Events with GPS Check-In and Loyalty Rewards

> Create in-app events with location-based check-in, loyalty point rewards, and optional ticket sales to drive physical attendance and engagement.

The Events module lets you promote any in-person occasion — from a weekend store sale to an annual trade fair — directly inside your app. Customers can discover your event, get directions, and check in on arrival to earn loyalty points or unlock a bonus reward. Combine events with push notifications and segment targeting to maximise attendance and reward the customers who show up.

## Configuration Reference

| Field                  | Description                                                                          |
| ---------------------- | ------------------------------------------------------------------------------------ |
| **Name**               | The event title displayed in the app.                                                |
| **Location**           | Free-text location name (e.g. "Main Store – Hamburg").                               |
| **Address**            | Full street address used to generate a Maps link for navigation.                     |
| **Latitude**           | GPS latitude coordinate for check-in geofencing.                                     |
| **Longitude**          | GPS longitude coordinate for check-in geofencing.                                    |
| **Description**        | Rich text description of the event — programme, dress code, what to bring, etc.      |
| **Start date/time**    | Date and time the event begins; check-in becomes active from this moment.            |
| **End date/time**      | Date and time the event ends; check-in is automatically disabled afterwards.         |
| **Check-in Punkte**    | Number of loyalty points awarded when a customer checks in.                          |
| **Check-in Belohnung** | Optional bonus item (coupon or goodie) granted at check-in, in addition to points.   |
| **Check-in Radius**    | GPS radius in metres within which check-in is permitted. Default: 250 m.             |
| **Ticket product**     | (Optional — requires Shop module) Link a shop product for paid advance ticket sales. |
| **Segment**            | Restrict event visibility to one or more customer segments.                          |
| **Client ID**          | Restrict event visibility to one or more apps in a multi-brand setup.                |

## Setting Up GPS Check-In

Check-in transforms physical attendance into a measurable, rewardable action. When a customer opens the event in the app and taps **Check in**, the app compares their GPS position to the coordinates you entered. If they are within the defined radius and the event time window is active, check-in succeeds and the reward is granted.

### Points and bonus rewards

* **Check-in Punkte** — enter the number of loyalty points a customer earns by checking in. This is the primary incentive; match the value to the significance of the event.
* **Check-in Belohnung** — optionally attach a coupon or goodie that is delivered automatically at check-in. Use this for exclusive giveaways, event-day discounts, or prize draws.

### Choosing the right radius

<Note>
  The default check-in radius of **250 metres** suits most retail or restaurant events where attendance is concentrated in one building. For open-air festivals, markets, or large trade fair venues, increase the radius to **500–1000 metres** to account for the physical spread of attendees and GPS drift in open spaces.
</Note>

### Time window

Check-in is only available between the **Start date/time** and **End date/time** you define. Outside this window, the check-in button is inactive — customers can still view the event but cannot claim the reward. Always set the end time generously to account for late arrivals.

## Ticketing (Optional)

If your Pocketshop account includes the **Shop module**, you can link a ticket product to any paid event to enable advance sales directly in the app.

1. Create the ticket as a product in your Shop module, including price and any available variants (e.g. standard, VIP).
2. Open the event and select the product in the **Ticket product** field.
3. A **Buy ticket** button will appear on the event detail screen, sending customers directly to the shop product page.

This flow is suitable for concerts, workshops, exclusive tastings, or any event where capacity must be managed or revenue collected in advance.

## Audience Filtering

Restrict which customers can see and interact with an event using the same filtering tools available across all Pocketshop content:

* **Segment targeting** — assign one or more segments to make an event visible only to that group. Use this for VIP-only evenings, regular-customer preview days, or employee gatherings.
* **Client ID targeting** — in multi-brand or franchise setups, assign Client IDs to ensure an event only appears in the relevant brand's app.

Leave both fields empty to make the event visible to all users across all apps.

## Creating an Event with GPS Check-In

<Steps>
  <Step title="Open the Events module and create a new event">
    Navigate to **Content → Events** in your Pocketshop dashboard and click **New event**.
  </Step>

  <Step title="Enter the event details">
    Fill in the **Name**, **Location**, **Address**, and **Description**. A clear, compelling description increases tap-through rates from the event list.
  </Step>

  <Step title="Add GPS coordinates">
    Enter the **Latitude** and **Longitude** of the event venue. Use Google Maps or a similar tool to obtain precise coordinates — accuracy here directly affects whether customer check-ins succeed.
  </Step>

  <Step title="Set the date and time window">
    Define the **Start date/time** and **End date/time**. Check-in will only be active between these two moments.
  </Step>

  <Step title="Configure the check-in reward">
    Enter the number of **Check-in Punkte** to award. Optionally select a **Check-in Belohnung** (coupon or goodie) for an additional reward at check-in.
  </Step>

  <Step title="Set the check-in radius">
    Enter the **Check-in Radius** in metres. Use 250 m for indoor or single-building venues; increase to 500–1000 m for large outdoor events.
  </Step>

  <Step title="Apply segment or Client ID targeting (optional)">
    If this event is exclusive to a particular customer group or brand, assign the appropriate **Segment** and/or **Client ID** values.
  </Step>

  <Step title="Save and publish">
    Save the event. Confirm it appears correctly in the app preview, then send a push notification to drive awareness and attendance.
  </Step>
</Steps>

<Tip>
  Schedule a push notification to go out 24–48 hours before the event and again on the morning of the event day. Reference the check-in reward explicitly in the message — "Check in today to earn 50 bonus points" — to give customers a concrete reason to engage.
</Tip>

## Best Practices

<Accordion title="Combine check-in points and a bonus reward for maximum participation">
  Points alone incentivise check-in, but adding a tangible **Check-in Belohnung** — a same-day discount coupon, a free item, or a prize-draw entry — creates a stronger pull, especially for first-time event attendees. Reserve the highest-value rewards for your most strategically important events.
</Accordion>

<Accordion title="Increase the GPS radius for large or outdoor venues">
  Indoor, single-building events work well with the default 250 m radius. For festivals, open-air markets, or multi-hall trade fairs, set the radius to 500–1000 m. GPS accuracy can vary by up to 50–100 m in open spaces, so a generous radius prevents false negatives that frustrate customers who are genuinely on site.
</Accordion>

<Accordion title="Use segment targeting for exclusive events">
  Not every event needs to be open to everyone. Preview evenings for loyal customers, wholesale days for trade buyers, or team events for employees all benefit from segment restrictions. Customers outside the segment will not even see the event in their feed, keeping the experience exclusive and the invite list tight.
</Accordion>

<Accordion title="Define exact start and end times — and review them before publishing">
  The check-in window is enforced strictly. An end time that is too early means late arrivals miss their reward; a start time that is too late means eager early-comers are frustrated. Build in a buffer of 15–30 minutes on each side of the event's scheduled programme, and always double-check the times before the event goes live.
</Accordion>
