Points Reporting

only users with finance permissions and above will have access to this section schedule a points report navigate to settings > alerts & reports > points reporting select a date, frequency, and input your recipients' emails you can optionally toggle the "report by store" to see the breakdown by each store note by store breakdowns do not contain points that are unassignable to a specific store (e g boosted or manually adjusted points by team members) save download a points report navigate to settings > alerts & reports > points reporting scroll down to the monthly financial report vault locate the report you wish to download and click the link to download you can download either the report by store or by persona points report contents see our points modifiers docid\ wy8vtkce6ixe4xinhj0h0 guide for more information on how your loyalty members earn points store report by month starting points any event prior to the start date of the report is put here month delta the difference between the starting points total of the current month vs the ending points total of the previous month why is there a points difference from one month to the next? loyalty reports are generated monthly there may be changes in points totals between the first and last day of the month that cannot be accounted for elsewhere in the report examples some persona merges and unmerges aiq loyalty settings adjustments pos/ecom delays or updates changes in data mapping to stores points' liabilities per store are fluid based on a persona's favorite store customers can manually assign their favorite store or be auto assigned based on their purchase history if a customer's favorite store is updated (manually or automatically) their points total will be un assigned from the previous store and assigned to the new location legacy points legacy point values (raw file import, pos import) points earned from sales, collectibles, and visits points boosted from boosts, multipliers, and referral sales points adjusted manual adjustments points multiplied points total added from audience transaction multiplier(s) points blocked points added to stop customers from becoming points negative points redeemed redemptions points expired any points that have expired points net legacy+earned+boosted+adjusted+multiplied+blocked redeemed expired ending points sum of all points adjustments and updates that occurred during the month persona report by month first name first name of the persona last name last name of the persona fav store favorite store id for the persona fav store state state location of the favorite store email email address of the persona mobile phone mobile phone number of the persona home phone home phone number of the persona src ids source identifier for the persona age age of the individual allowed sms whether persona is opted into sms communications optout time time in time/date the customer opted out of communications with your store allowed email a boolean indicating if email communication is permitted for the individual allowed push a boolean indicating if push notifications are permitted for the individual allowed direct mail a boolean indicating if direct mail communication is permitted for the individual allowed phone a boolean indicating if phone calls are permitted for the individual loyalty number the loyalty program number associated with the individual loyalty status the status of the individual's loyalty program membership join date the date the individual joined the loyalty program starting balance starting balance of points for the month accrued points accrued for the month redeemed points redeemed for the month expired points expired for the persona this month adjustments manual and aiq adjustments made to the personas points balance point modifiers audience based points modifiers (boost/mutipliers/etc ) for the month spent amount the persona spent in $ ending balance starting balance of points for the month date of last sale in range date of the last sale made to the persona within the timeframe of the report if the last sale was within the timeframe of the report, it will show a date in this column if the last sale was prior to the timeframe of the report, it will show as blank date of last sale all time date of the last sale for this persona all time (not restricted to the timeframe of the report) merged ids list of persona ids merged into the current active persona detailed report by month uid a unique identifier for the aiq account contact id a unique identifier for the contact source id an identifier indicating the source, which sometimes includes a specific tag (e g , 43401586 hellohigh) platform the platform from which the data is sourced (e g , pos, file upload, etc ) receipt id a unique identifier for the receipt, applicable for certain transactions fav store id an identifier for the favorite store attached to the event event the type of event recorded (e g , sale, redemption, legacy) "start" prefix identifies the starting points for the month for the associated contact id assigned store id the identifier for store the event has been assigned to point value the point value associated with the event timestamp the timestamp of the event, which is in unix epoch time points reports generated via audiences points reports can be pulled for specific audiences to show points totals for personas who are currently in the audience at the time the report is run, regardless of the date range ran this means that points calculations and reporting generated through the audience builder will retroactively change as merges occur the logic reflected in the points reports generated via audiences reflects the current logic in the account and does not reflect the logic in the account for the time frame in question points reports generated multiple times for a specific audience will vary over time and will not remain consistent because points reports generated for audiences will inherently change over time, they are considered dynamic and should not be used to determine the financial liability from outstanding loyalty points examples of changes in historical audience points reports (and why they should not be utilized) change in expiration logic loyalty program begins jan 1, 2022 expiration logic is changed on june 1, 2022 and applied retroactively however, from jan 1 2022 through may 31st, 2022, that expiration logic was not implemented therefore, actual financial liability of usable loyalty points during jan 1 2022 through may 31st, 2022 should not incorporate expiration logic as that logic did not exist at that time however, audience points report will incorporate the expiration logic from jan 1 2022 through may 31st, 2022 as audience points reports utilize the existing logic for the historical timeframe and not the historical logic when reporting on the historical timeframe merges in august 2022, i was incorrectly merged with an unrelated persona as the staff was using dummy contact information when collecting contact information at check out this resulted in me having 300 points for august 2022 however, in october, it was discovered that i incorrectly was merged with another unrelated individual so, in october 2022 i was unmerged resulting in me having a remaining point balance of 200 points (as 100 points were a result of the ‘bad merge’ and were therefore removed once the bad merge was corrected) if the august 2022 report is regenerated after october 2022, my outstanding point balance will reflect my ‘un merged’ account with 200 points instead of the ‘merged account’ with 300 points that was seen the first time the report was generated this would cause variable financial liability as a result of the variable outstanding point balances seen within the same report, generated at different times (pre aug 202 vs post oct 2022) points reporting faqs how do members earn points? transactions \[total spent on transactions] x \[point accrual ratio] visits \[number of visits] x \[point per visit] boosts, gifts, and multipliers see points modifiers docid\ wy8vtkce6ixe4xinhj0h0 manual adjustments when a staff member manually adds or subtracts points from an account api driven integration partners connected integrations can cause points to be added/subtracted block adjustments see points modifiers docid\ wy8vtkce6ixe4xinhj0h0 how do i verify the points report? if your pos sends aiq transcation ids you can access the discounts and the transactions they were applied to via the api if your pos does not send aiq transaction ids or you use “groupon style” redemption methods (e g the customer shows staff discounts and redeems via phone and not directly in the pos) you will not be able to tie redemptions to exact sales within aiq an alternative is to pull discount usage from your pos directly and match it to utc timestamps from redemptions that occurred within your aiq ledger this can be done by downloading the csv on the analytics > members club tab on the points report, why would points multiplied be more than points earned? points earned is from sales, collectibles, and visits only points multiplied is an audience multiplier so more points were earned and are eligible for multiplication than earned via standard methods (sales, collectibles, visits) if you are looking for the total, points net is the total change from the previous month (including subtracting points redeemed) how does the meaning of “legacy points” differ between loyalty reporting and expiration settings? in loyalty reporting “legacy points” here usually means points that existed before the current loyalty tracking period or before a loyalty program changeover they’re included in the total for historical accuracy but may not behave like new points in terms of expiration in expiration / expire all logic in this context, “legacy points” refers to older points carried over from before the current expiration rules were applied they might be expired in bulk when doing an “expire all” action, or in some setups, they’re excluded from expiration runs depending on your program’s settings how are points from campaign giveaways calculated? these are typically awarded based on the configuration inside the specific campaign setup in most cases you set a fixed number of points that each participant (or winner) gets aiq then applies those points directly to the contact’s loyalty balance once the campaign ends or when the trigger condition is met there’s no dynamic calculation (like based on spend or tier) unless you explicitly configure it to use a multiplier