Getting events automatically added to Google Calendar

I've made a site to manage workshops I run for improv comedy. I want the confirmation emails to automatically add events to Google Calendar.

The markup I include in my emails is validated at Below is the full original source of the email I've sent. It's been validated at https://www.google.com/webmasters/markup-tester/

I am using the "reservationStatus": "http://schema.org/Confirmed" This is as specified in the Google docs. I originally used the status "ReservationConfirmed" instead of just "Confirmed" since that's what schema.org seems to use (they don't have a 'Confirmed').

But neither 'ReservationConfirmed' or 'Confirmed' get added.

I've added ticket info, with TicketToken pointing to a correct QR code. I've added "performer" info (me, as the teacher) which is what Google EMail Markup Validator suggested.

I've also tested this by sending emails to myself (i.e. from [email protected] to [email protected]) which is supposed to bypass the need for an email to be whitelisted.

Received-SPF: pass (google.com: domain of [email protected] designates 72.52.242.236 as permitted sender) client-ip=72.52.242.236;
Date: Thu, 21 Dec 2017 10:53:10 -0800 (PST)
Message-Id: <[email protected]>
From: [email protected]
Reply-To: [email protected]
Subject: ENROLLED: test - Mon Dec 25 - 11:00am-5pm
To: [email protected]
MIME-Version: 1.0
Content-Type: text/html
charset: iso-8859-1

<script type="application/ld+json">
 {
   "@context": "http://schema.org",
   "@type": "EventReservation",
   "reservationNumber": "wbhwk794",
    "reservationStatus": "http://schema.org/Confirmed",
   "underName": {
     "@type": "Person",
     "name": "Will Hines"
   },
   "reservationFor": {
     "@type": "EducationEvent",
     "name": "test",
     "startDate": "2017-12-25 11:00:00",
      "endDate": "2017-12-25 17:00:00",
     "performer": {
          "@type": "Person",
          "name": "Will Hines",
          "image": "http://willhines.net/home_files/wh_clay_med.jpg"
        },
     "location": {
       "@type": "Place",
       "name": "The Complex",
       "address": {
         "@type": "PostalAddress",
         "streetAddress": "6476 Santa Monica Blvd",
         "addressLocality": "Los Angeles",
         "addressRegion": "CA",
         "postalCode": "90038",
         "addressCountry": "US"
       }
     }
   },
    "ticketToken": "http://www.willhines.net/practices/code.php?wid=52&key=9ef66eb1f8166930&v=winfo",
    "ticketNumber": "1",
    "numSeats": "1",
   "modifiedTime": "2017-12-21 10:53:05",
   "modifyReservationUrl": "http://willhines.net/practices/index.php?wid=52"
 }
 </script>
<p>You are ENROLLED in test - Mon Dec 25 - 11:00am-5pm. </p>

<p>To DROP, click here:
http://localhost:8888/practices/index.php?key=9ef66eb1f8166930&ac=drop&wid=52<br><br>Pay in person or venmo. On the day of the workshop is fine.<br>Venmo link:
http://venmo.com/willhines?txn=pay&share=friends&amount=10&note=improv%20workshop</p>

<p>Full info:</p>

<p><b>Title:</b> test<br>
<b>When:</b> Mon Dec 25 - 11:00am-5pm<br>
<b>Where:</b> The Complex 6476 Santa Monica Blvd Los Angeles CA 90038<br>
<b>Cost:</b> 10</p>
<b>Description:</b> </p>






<p>Thanks!</p>

<p>-Will Hines<br>
HQ: 1948 Hillhurst Ave. Los Angeles, CA 90027</p>

Solution

In case anyone else runs into this, I "solved" it. Minor schema error, plus I had to register my email with Google.

1) When the Google docs differ from what's said on schema.org, follow the Google docs. For me that meant defining the reservationFor @type as "Event" not "EducationEvent"

2) You need to register your email with google as described here: Registering With Google

Otherwise, tests will only work if you do them via script.google.com as described in Apps Script Quickstart.

The docs say you can sidestep being registered for testing by having you email sent from and to the same address, but I was not able to get that to work.

3) Also, and this is likely obvious, but I had my PHP code connect (Via PEAR's Mail) to a SMTP server where I had an account. This made sure my email had valid DKIM/SPF info.