Tech Stack: 6Purpose: Assign custom post to the claimant and sync dataExplanation: After a course operator claims their listing, we need to trigger some workflows within WordPress to

Tech Stack: 4Purpose: Assign dynamic commissions based on referral of golf courses.Explanation: Because commissions vary by state, it didn’t make sense to give the same amount across the

Tech Stack: 3Purpose: Find hot leads and clear email inboxExplanation: Similar to the previous scenario, this one tracked opens and clicks from a chrome extension. Triggered hourly, it

Tech Stack: 1Purpose: Track email open counts to determine warm/hot leadsExplanation: In another scenario, we email golf courses and implant a webhook pixel into the email to track

Tech Stack: 3Purpose: Live pricing as offers are added or removedExplanation: Triggered by the Golf Course Edits scenario, this scenario counts the number of golf courses per state

Tech Stack: 7Purpose: Update and sync information across platforms when edits submittedExplanation: Golf courses or admins can revise their offers or business details via Gravity Forms. We use

Tech Stack: 7Purpose: Validate registration codes from gifts and 3rd party vendorsExplanation: Codes are sold from our website and through 3rd parties vendors. Because we wanted to lower

Tech Stack: 12Purpose:Complete order processing workflowsExplanation: This scenario is triggered by another scenario that sorts orders by ProductID. In this case, the buyer purchased either a digital