In the State Changers meeting, the main topics discussed revolved around reward programs, affiliate purchases, mechanisms to verify the said purchases, and methods to deal with potential fraud. The participants discussed the problem of not being able to account for purchases made through Amazon since the company doesn't yet have access to Amazon's API.
One solution proposed was to award points based on the click of the redeem button rather than confirmed purchases. However, a cron job was proposed to periodically check user behaviour and possibly nullify the rewards if the user is just clicking without making a purchase. To fine-tune this methodology, they contemplated adding a system for users to verify their purchases manually. The meeting also involved considerations about enhancing data collection for better insights. The participants touched upon using CSV files for raw data and possibly using tools like Zapier for managing the same. Another discussed strategy was to understand the Amazon affiliate system better and determine potential routes to access the necessary data for verification, such as daily reports or other mechanisms Amazon uses. Finally, the participants discussed integrating tools like Customer IO and Mixpanel for tracking events and user behaviours, which might assist in identifying system abuse or anomalies. However, they acknowledged the need to understand and close the existing data black holes for a more comprehensive and reliable overview. The meeting did not specifically mention Xano, WeWeb, FlutterFlow, Make, Integromat, Outseta, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI or AI21.
(Source: Office Hours 10/16/2023 )
