Description: Previously, all rewards/benefits/points were awarded to all brand members regardless of whether they knowingly participated in earning the points/award. This may not reflect a member’s interest in the benefit/reward. This enhancement allows brands to create their own campaigns that target member behaviors or patterns to incentivize members to actively participate and earn loyalty benefits for completing specific milestones. 

Prerequisites:

• Enable the “Activation Required” flag, which is available within the campaign configuration. The flag can be enabled by an Annex Cloud administrator.
• Activation API is required to enroll in the campaign.

Use Cases: A brand wants to enable a campaign that requires a member to purchase a specific product in order to receive the points/award. The only way the member can get the reward is that the member will need to opt-in to activate the campaign before his purchase is recognized as part of the campaign. Create a campaign that requires activation, ensuring members willingly enroll to participate and earn benefits.

The above use case gets executed in the following steps:

• Enable “Activation Required” flag
• Create a campaign where “Activation Required” flag is enabled. 
• Target members activate the campaign via Activation API. 
• Target members fulfill the campaign condition. 
• The associated benefit is awarded.

For more details on this enhancement, please visit the Annex Cloud Campaigns help documentation page.

It allows a brand to create campaigns where its members must opt in to participate and earn benefits.

Brands can analyze members' interest in each campaign and engage with them more personally.

Brands can send reminders to enrolled loyalty members who haven't participated or run surveys for non-enrolled members to gather feedback and encourage them to join.

Description: This enhancement allows brands to create a campaign where they can offer loyalty members different validity dates for the same benefit. This feature allows brands to: 

1. Create a campaign with a general validity period.
2. Assign each member a personalized validity period within the campaign's overall duration.
3. Allow members to participate only during their assigned periods.
4. Send new validity periods to members multiple times within the campaign's overall duration, enabling members to participate more than once.

Prerequisites:

• The "Apply Individual Validity" flag should be enabled by a brand administrator and is available within campaign configuration. 
• Individual validity API is required to send the target member’s campaign validity period. 

Use Cases: A brand wants members to focus on a specific campaign. We can assign different validity dates to the target members within a campaign duration so that the members can participate and earn benefits during their valid dates only.

The above use case gets executed in the following steps:

• Create a campaign where “Apply Individual Validity” flag is enabled. 
• Brand sends the individual validities of members via individual validity APIs. 
• Target members fulfill the campaign conditions within their validity period. 
• The associated benefit is awarded. 

For more details on this enhancement, please visit the Annex Cloud Campaigns help documentation page.

This enhancement ensures brand members only engage in the campaign during the defined validity windows, as determined by the brand.

It removes the need for multiple or redundant campaigns.

Description: This enhancement allows brands to group multiple campaigns together. At the group level, a brand can set different precedence rules to decide what action to take when a member qualifies for multiple campaigns at once.

Prerequisites: The “Enable Campaign Group” flag must be enabled by an administrator in the Super Admin to use this functionality. 

Use Cases:

1. Award members the benefits of all valid campaigns if they meet the conditions for multiple campaigns in a single activity. This will ensure they feel delighted about achieving multiple rewards simultaneously.

The above use case gets executed in the following steps:

• Create a campaign group.
• Add the applicable campaigns to it.
• Select the precedence rule as "All eligible campaigns should be applied at a time". 
• The target member fulfills the conditions of three campaigns in a single activity and earns the benefit of all three campaigns.

2. Set the rule to apply the campaign with the highest points when a member qualifies for multiple campaigns in a single activity. This ensures the member receives the best benefit. This also helps control liabilities by not awarding multiple campaign benefits.

The above use case gets executed in the following steps:

• Create a campaign group. 
• Add the applicable campaigns to it. 
• Select the precedence rule as “Highest points campaign should be applied at a time”. 
• When a member qualifies for three campaigns in a single activity, they receive the benefit of the campaign with the highest points. 

For more details on this enhancement, please visit the Annex Cloud Campaign Group help documentation page.

• Setting the campaign precedence rule at a group level provides greater flexibility, allowing brands to tailor campaign rules to specific groups rather than applying a one-size-fits-all approach at the site level.
• Enhances the ability to manage campaigns more effectively by considering the unique needs and behaviors of different groups, which helps in better managing liabilities.

Audience:

Description: This enhancement allows you to create a campaign with multiple conditions, each offering unique benefits. This flexibility wasn't available before, so we're improving campaigns to include conditional variants as segments. Each segment can be pulled into a campaign milestone and can have its own benefits.

Prerequisites: None

Use Cases: Create a "Spend more earn more" campaign where members who spend between 100-200 should earn 2x points and the members who spend between 201-500 should earn 3x points.

The above use case gets executed in the following steps:

• Create two segments, one with the amount spend condition of 100-200 (let's call it Segment A) and the second one with the amount spend condition of 201-500 (Segment B).
• Create a campaign where one milestone will have Segment A, milestone action as Purchase and benefit as 2x. Another milestone will have Segment B, milestone action as Purchase and benefit as 3x. 
• A member spends 150 and earns 2x from the above campaign. 
• A member spends 300 and earns 3x from the same campaign. 

For more details on this enhancement, please visit the Annex Cloud Campaigns help documentation page.

• Brands can create a single campaign with multiple conditions and benefits.
• All of a campaign’s data is consolidated under one umbrella, enabling comprehensive analysis and reporting.

Description: This feature enables the separate tracking of campaign milestone benefits using Action ID 178. Currently, it does not support distinguishing and monitoring the original action points from the campaign milestone points.

Prerequisites: The "Display Separate Campaign Milestone Activity" Super Admin flag should be activated to view the individual activities for campaign milestone benefits. The Points API supports this feature when enabled, while the new Issuance (Order) API will exhibit this behavior by default.

Use Cases: Different member behaviors are separated so a brand can implement incentives or benefits to better engage with its customers.

1. If a member spends >= 1000 on the order, they will receive 2x points.
   • For an order total spend of 1000, the potential points awarded will be 1000 (based on a 1x ratio). 
   • The milestone to monitor orders/spend from the issuance API is set at action 174. 
   • The member should be awarded a total of 2000 points. 
   • This comprises 1000 Base Points AND 1000 Campaign Milestone Benefit Points. 
   • Two activities need to be generated: 1000 points for action ID 174 - Base Points, and another 1000 points for action ID 178 - Campaign Milestone Benefit Points. 
2. When a member signs up for the newsletter within a specific time frame, they will receive 1000 points.
   • The action ID for newsletter sign-up is 102, with 500 action points allocated.
   • Upon signing up, the member will receive a total of 1000 points. 
   • This transaction includes 500 base points for action ID 102 and 500 campaign milestone benefit points for action ID 178. 
3. An additional 1000 points is awarded on top of the original action points when a member signs up for the newsletter within a specific time frame.
   • The action ID for newsletter sign-up is 102, with 500 action points allocated.
   • Upon signing up, the member will receive a total of 1500 points. 
   • This transaction includes 500 base points for action ID 102 and 1000 campaign milestone benefit points for action ID 178.

For more details on this enhancement, please visit the Annex Cloud Campaigns help documentation page.

Description: This new API enables the processing of orders. It accepts the values (spend, points, attributes) provided by the brand in the request and grants the corresponding benefit to the loyalty member without any alterations. This API differs from the conventional approach of processing orders, which involves utilizing an in-house points system and spend calculation mechanism. 

Use Case:

• The objective is to handle order processing within the loyalty system. The management of spending and points calculations has already been addressed by the third-party system. The API is designed with the ability to receive values, process orders, and grant the benefits requested. 
• Adds the capability to place orders on hold. The management of these holds can differ, allowing me the flexibility to determine which orders should be placed on hold and which ones should not. 
• Adds the capability to edit and adjust the current order that is on hold (not confirmed yet). This modification can encompass changes related to expenditures, points, attributes, product data, and more. 

For more details on this enhancement, please visit the following Annex Cloud Issuance API - Segmentation help documentation page.