Loyalty Campaign Object
STATIC: vouchers need to be manually publishedAvailable values:AUTO_UPDATE,STATIC| | voucher | See: Loyalty Card | | auto_joinboolean| Indicates whether customers will be able to auto-join a loyalty campaign if any earning rule is fulfilled. | | join_onceboolean| If this value is set totrue, customers will be able to join the campaign only once. | | use_voucher_metadata_schemaboolean| Flag indicating whether the campaign is to use the voucher’s metadata schema instead of the campaign metadata schema. | | start_datestring| Activation timestamp defines when the campaign starts to be active in ISO 8601 format. Campaign is inactive before this date.Example:2022-09-20T00:00:00.000Z | | expiration_datestring| Expiration timestamp defines when the campaign expires in ISO 8601 format. Campaign is inactive after this date.Example:2022-09-30T00:00:00.000Z | | validity_timeframe | See: Validity Timeframe | | validity_day_of_week | See: Validity Day Of Week | | validity_hours | See: Validity Hours | | activity_duration_after_publishingstring| Defines the amount of time the vouchers will be active after publishing. The value is shown in the ISO 8601 format. For example, a voucher with the value of P24D will be valid for a duration of 24 days. | | descriptionstring| An optional field to keep any extra textual information about the campaign such as a campaign description and details. | | vouchers_countinteger| Total number of unique vouchers in campaign. | | activeboolean| A flag to toggle the campaign on or off. You can disable a campaign even though it’s within the active period defined by thestart_dateandexpiration_date.-trueindicates an active campaignfalseindicates an inactive campaign | | metadataobject| The metadata object stores all custom attributes assigned to the campaign. A set of key/value pairs that you can attach to a campaign object. It can be useful for storing additional information about the campaign in a structured format. | | created_atstring| Timestamp representing the date and time when the campaign was created. The value is shown in the ISO 8601 format.Example:2021-12-01T08:00:50.038Z | | updated_atstring| Timestamp representing the date and time when the voucher was updated. The value is shown in the ISO 8601 format.Example:2022-09-20T09:18:19.623Z | | creation_statusstring| Indicates the status of the campaign creation.Available values:DONE,IN_PROGRESS,FAILED,DRAFT,MODIFYING| | vouchers_generation_statusstring| Indicates the status of the campaign’s vouchers.Available values:DONE,IN_PROGRESS,FAILED,DRAFT| | protectedboolean| Indicates whether the resource can be deleted. | | access_settings_assignments | See: Access Settings Campaign Assignments List | | category_idstring| Unique category ID that this campaign belongs to.Example:cat_0b688929a2476386a7 | | categories | See: Category | | loyalty_tiers_expirationobject| Defines the expiration mechanism for loyalty tiers.One of: Balance, Points in Period | | objectstring| The type of the object represented by JSON. This object stores information about the campaign. |
Loyalty Card
Validity Timeframe
Validity Day Of Week
Integer array corresponding to the particular days of the week in which the voucher is valid.0Sunday1Monday2Tuesday3Wednesday4Thursday5Friday6Saturday
Validity Hours
Access Settings Campaign Assignments List
Category
Balance
Points in Period
Areas and Stores Campain Assignment
Balance Drop
Custom
Calendar Periods
QUARTER: The expiration date will be rounded to the end of the quarter.HALF_YEAR: The expiration date will be rounded to the half year.YEAR: The expiration date will be rounded to the end of the year.Available values:MONTH,QUARTER,HALF_YEAR,YEAR| | strategystring| Which portion of the given period should the rounding be applied to.Available values:END|
Specific Month
1: February2: March3: April4: May5: June6: July7: August8: September9: October10: November11: December |
