Wecheer Source
Source Info
- The Wecheer Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
- This source is in Beta
Wecheer is a customer-engagement platform for consumer goods brands selling through third-party points of sale.
This is an Event Cloud Source which exports data into your Segment warehouse and also federates the exported data into your other enabled Segment destinations.
Wecheer maintains this source. For any issues with the source, contact the Wecheer Support team.
- From your workspace's Sources catalog page, click Add Source.
- Search for Wecheer in the Sources Catalog, select Wecheer, and click Add Source.
- Give the source a name and configure any other settings.
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example,
Wecheer_Prod,Wecheer_Staging,Wecheer_Dev).
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example,
- Click Add Source to save your settings.
- From your Wecheer settings page in the Segment UI, copy your write key.
- Log in to your Wecheer account and navigate to Campaigns > Advertisers > Advertiser Details > Advertiser Settings > Outbound Events > Choose Provider > Segment and paste the key to connect.
- Select the list of events that you want to subscribe to.
- Click Save configuration.
Wecheer uses this Segment Event Cloud Source to send Wecheer event data to Segment. Events are sent using Segment's server-side methods (such as Track, Identify, Page, and Group), depending on the type of data being recorded.
Each event includes the identifiers described in the Event Properties section (for example UserId, AdvertiserId, and CampaignId), so that downstream tools and your data warehouse can reliably join Wecheer activity back to your own users, brands, and campaigns.
Once events are delivered to Segment, they are:
- Forwarded to any destinations that support server-side events
- Written into the schema that Segment creates for this source in your data warehouse, so you can query them using SQL.
The following table lists all event types that Wecheer Campaigns can send to Segment when you configure outbound events at the Advertiser or Campaign level.
Each of these events is sent as a Segment Track call with the Event Name as the event value.
| Event name | Description |
|---|---|
| Card Received | User receives a loyalty card |
| Card Given | Card issued to user |
| No Campaign Joined | User has no active campaign |
| Consumption | General consumption event |
| Consumption Match | Consumption matches criteria |
| First Consumption | User's first purchase |
| Any Consumption | Any consumption occurred |
| First Consumption Given | First purchase reward given |
| Any Consumption Given | Any consumption reward given |
| Scan Receipt | Receipt scan initiated |
| Receipt Scanned | Receipt successfully scanned |
| Receipt Triaged | Receipt moved to triage |
| Receipt Failed | Receipt processing failed |
| Receipt Fraud | Fraudulent receipt detected |
| Receipt Incomplete | Receipt data incomplete |
| Receipt No Reward | Receipt doesn't qualify for reward |
| Receipt Manual Review Limit Exceeded | Manual review queue full |
| Stamps Given | Stamps awarded to user |
| Manual Give Stamps | Stamps manually added |
| Punchcard Stamps Received | User receives punchcard stamps |
| Stamps Limit Reached | User reached stamp limit |
| Stamps Overflow | Stamps exceed limit |
| Punchcard Completed | Punchcard fully completed |
| Punchcard Step Completed | Punchcard step achieved |
| Punchcard Already Completed | Duplicate completion attempt |
| Reward Received | User receives reward |
| Birthday Reward Received | Birthday reward given |
| Level Unlock Reward Received | Level-up reward given |
| Validate Reward | Reward validation performed |
| Points Received | User receives points |
| No Point Received | No points awarded |
| Lucky Draw Received | User receives lucky draw entry |
| User Data Shared | User shares personal data |
| Game Triggered | Game initiated |
| Game Completed | Game finished |
| Level Unlocked | User unlocks new level |
| Safe Box Generated | SafeBox created |
| Safe Box Read | SafeBox accessed |
| Safe Box Redeemed | SafeBox redeemed |
| Catalog Redeem | Catalog item redeemed |
| Products Limit Reached | Product limit hit |
| Staff Products Given | Staff issues product |
| Manual Verification Requested | Manual review requested |
| Manual Verification Approved | Manual review approved |
| Manual Verification Rejected | Manual review rejected |
| Consumer Referral Invite Generated | Consumer referral created |
| Staff Referral Invite Generated | Staff referral created |
| Init Staff Point Card | Staff point card initialized |
| Handshake QR Valid | Valid QR code scanned |
| Handshake QR Invalid | Invalid QR code scanned |
| Data Consumer Sync | Consumer data synchronized |
| Advertiser Consumption Transaction | Transaction recorded |
The following table lists the properties included in the events listed above:
| Property name | Description |
|---|---|
user_id | ID of the user |
advertiser_id | Brand ID |
campaign_id | Campaign ID |
Once your Source is set up, you can connect it with destinations.
Log in to your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don't appear, check the Event Delivery tool, and refer to the destination docs for each tool for troubleshooting.
If there are any issues with how the events are arriving to Segment, contact the Wecheer support team.