Date Replacement Code in Groundhogg
{date.Y-m-d|+ 14 days} works to send a date two weeks in the future, no quotes, as one might think from looking at the PHP documentation.
{date.Y-m-d|+ 14 days} works to send a date two weeks in the future, no quotes, as one might think from looking at the PHP documentation.
For some reason, this seems to be a deep, dark secret of the Internet. Lesson completions are stored in the lifterlms_user_postmeta table. YMMV – You can try renaming that table if you don’t mind resetting all the completions…sometimes, that’s just the thing… This was related to a Groundhogg project, so sorry for the apparently errant…
So, Groundhogg has some bad habits and some punishing ones One bad habit is that forms only exist in funnels, as steps. That makes them really easy to delete, especially if you copy a funnel, and are not really careful whether you are in funnel 1 or funnel 2… The punishing part is that Groundhogg…
I am pretty sure this works…YMMV – It’s a little brutish, sorry. Create View posts2update AS SELECT p.id, m1.meta_value AS email from ayq_posts p, ayq_postmeta m1, ayq_postmeta m2 WHERE p.ID = m1.post_id and p.ID = m2.post_id AND m1.meta_key = ‘_billing_email’ AND m1.meta_value IS NOT NULL AND m2.meta_key = ‘_customer_user’ AND m2.meta_value = 0 Create View…
There is way to do this in the current version of the Groundhogg LifterLMS extension. However, if you create a custom field, and implement this, from the always generous Poobah of Groundhogg, Adrian Tobey… You can set a Lead Score rule based on the value of the custom field.
The simplest and no-code approach to this seems to be to use Superlinks. Create the Superlink, and embed it in your email or page. Set a tag to be added on click. Use that Tag Added Benchmark in the funnel builder to catch the event, then the Add Note action with something like {date.Y-m-d|now};Video Watched;ID=12345…
The Groundhogg WooCommerce integration by default will tag the Contact with a tag for the base product, but tagging variations is not possible in the existing extension. We have solved this issue…updating variation tags on Contacts for past orders, and tagging on new orders as well. We also have some ancillary code to generate the…