Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Jika sudah siap meluncurkan email dinamis kepada pengguna, Anda harus mendaftar ke Google untuk setiap alamat email pengirim yang Anda gunakan. Anda hanya
perlu mendaftarkan email satu kali meskipun konten email Anda berubah atau alamat email
pengirim yang sama digunakan untuk kasus penggunaan lain pada masa mendatang.
Untuk mendaftarkan email pengirim, selesaikan langkah-langkah berikut:
Kirim email asli yang siap produksi yang berasal dari server produksi Anda
(atau server dengan header SPF/DKIM/DMARC/From:/Return-Path: yang serupa)
termasuk bagian MIME email dinamis ke
ampforemail.whitelisting@gmail.com. Kami memerlukannya untuk memeriksa apakah Anda
mematuhi semua panduan dan persyaratan.
Saat Anda mengirim email ini, lakukan hal berikut:
Pastikan versi AMP email sudah benar sebelum
mengirim email dengan
mengujinya di Gmail
Kirim email secara langsung, bukan meneruskannya. Gmail
menghapus bagian MIME AMP saat meneruskan email.
Isi formulir pendaftaran
dan tunggu respons kami. Kami akan berusaha merespons sebagian besar permintaan dalam waktu 5 hari kerja.
Partisipasi Anda sebagai pengirim email dinamis tunduk pada kepatuhan terhadap
panduan Mencegah email ke pengguna Gmail diblokir atau dikirim ke
spam, yang
dapat berubah sewaktu-waktu tanpa pemberitahuan. Anda bertanggung jawab untuk memastikan kepatuhan
dengan pedoman saat ini. Partisipasi Anda dapat dicabut kapan saja jika
penyalahgunaan atau pelanggaran kebijakan ditemukan, atau atas pertimbangan Google. Kami dapat
meminta informasi tambahan selama proses pendaftaran atau setelah
pendaftaran selesai untuk memverifikasi kepatuhan Anda.
Panduan pendaftaran
Anda harus memenuhi panduan berikut agar berhasil mendaftar ke
Google:
Anda harus mengirim contoh email nyata dengan kualitas produksi, bukan contoh demo atau "Halo
Dunia". Jangan masukkan string placeholder seperti {name} dan {count} atau
string pengujian seperti [Test], [Proof mail], dan [Sample] di subjek atau
isi email Anda.
Email harus memiliki bagian MIME HTML atau teks yang serupa. Ada banyak instance
yang menampilkannya, seperti saat pengguna menonaktifkan email dinamis.
Email tidak boleh memiliki bug.
Anda harus mengautentikasi email menggunakan SPF, DKIM, dan DMARC seperti yang dijelaskan dalam Persyaratan keamanan.
Pastikan Anda telah meninjau praktik terbaik AMP untuk Email, dan bahwa
email Anda sesuai dengan saran di sana.
Pendaftaran berfungsi berdasarkan alamat email pengirim. Jika Anda ingin
mendaftarkan lebih dari satu alamat email pengirim, setiap alamat harus
didaftarkan secara terpisah dan harus mengirim email berkualitas produksinya sendiri.
Hal ini berlaku meskipun alamat email terpisah memiliki domain yang sama, karena
pendaftaran tidak berfungsi berdasarkan domain email pengirim.
Anda tidak boleh mengizinkan pihak ketiga, seperti pengguna atau masyarakat umum, untuk
menulis dan mengirim email secara langsung. Email yang Anda kirim dapat berisi
konten buatan pengguna, seperti postingan atau komentar. Alat pengujian dan "tempat
pengujian email" tidak dapat diizinkan dan harus mengandalkan langkah-langkah
yang diuraikan dalam Menguji email AMP di
Gmail.
eTLD+1 alamat email pengirim yang akan didaftarkan harus ditayangkan atau dialihkan ke situs yang valid (misalnya, bukan domain yang diparkir) milik pengirim. Misalnya, jika alamat email pengirim adalah noreply@mail.example.com, maka
https://example.com harus menayangkan situs. Situs harus dapat diakses
di seluruh dunia tanpa memerlukan filter IP.
[null,null,["Terakhir diperbarui pada 2025-03-24 UTC."],[],[],null,["# Register with Google to send dynamic emails\n\nWhen you are ready to launch your dynamic emails to your users, you must\nregister with Google for each sender email address that you use. You only\nneed to register the email once even if your email content changes or the same\nsender email address is used for another use case in the future.\n\nTo register a sender email, complete the following steps:\n\n1. Make sure that you meet all the [guidelines and requirements](#registration_guidelines) listed below.\n2. Send a real, production-ready email coming from your production servers\n (or a server with similar SPF/DKIM/DMARC/`From:`/`Return-Path:` headers)\n including the dynamic email MIME part to\n `ampforemail.whitelisting@gmail.com`. We need this in order to check that you\n comply with all the [guidelines and requirements](#registration_guidelines).\n As you send this email, do the following:\n\n 1. Make sure that the AMP version of the email is correct prior to sending the email by [testing it in Gmail](/workspace/gmail/ampemail/testing-dynamic-email)\n 2. Send the email directly instead of forwarding it. Gmail removes AMP MIME parts when forwarding an email.\n\n | **Caution:** Google will reject your registration application if you don't send an email for review, if you send a test (blank) email, or if you send an email that doesn't contain an AMP MIME part. Don't add `ampforemail.whitelisting@gmail.com` to your mailing list because it might cause many static HTML emails to be sent, which don't contain AMP MIME parts. At the time of review, Google only opens the most recently received email from the sender email address to register.\n3. Fill out the [registration form](https://forms.gle/fDqLE1gh4wMB6BeQ6)\n and await our response. We aim to respond to most requests within 5 working\n days.\n\nYour participation as a sender of dynamic email is subject to compliance with\nthe [Prevent mail to Gmail users from being blocked or sent to\nspam](https://support.google.com/mail/answer/81126) guidelines, which are\nsubject to change without notice. You are responsible for ensuring compliance\nwith the current guidelines. Your participation may be revoked at any time if\nabuse or policy violations are discovered, or at Google's discretion. We may\nrequest additional information during the registration process or after\nregistration is complete to verify your compliance.\n\nRegistration guidelines\n-----------------------\n\nYou must meet the following guidelines in order to successfully register with\nGoogle:\n\n- You must send a real, production-quality example email, not a demo or \"Hello World\" example. Don't put placeholder strings like `{name}` and `{count}` or test strings like `[Test]`, `[Proof mail]` and `[Sample]` in your subject or body.\n- Emails must have a similar HTML or text MIME part. There are many instances where this is shown instead, such as when the user has disabled dynamic email.\n- The email must have no bugs.\n- You must authenticate the emails using SPF, DKIM and DMARC as detailed in the [Security\n requirements](/workspace/gmail/ampemail/security-requirements).\n- Ensure that you have reviewed the AMP for Email best practices, and that your email conforms to the suggestions there.\n- Registration works on a per-sender-email-address basis. If you want to\n register more than one sender email address, each address needs to be\n registered separately and needs to send its own production-quality email.\n\n This is true even if the separate email addresses have the same domain, as\n the registration doesn't work on a per-sender-email-domain basis.\n- You mustn't allow third parties, such as users or the general public, to\n directly author and send emails. The emails you send can contain\n user-generated content, such as posts or comments. Testing tools and \"email\n playgrounds\" can't be whitelisted and should instead rely on the steps\n outlined in [Test your AMP emails in\n Gmail](/workspace/gmail/ampemail/testing-dynamic-email).\n\n- Emails must follow the [Prevent mail to Gmail users from\n being blocked or sent to spam](https://support.google.com/mail/answer/81126)\n guidelines.\n\n- A low rate of spam complaints from users.\n\n- The [eTLD+1](https://developer.mozilla.org/en-US/docs/Glossary/eTLD)\n of the sender email address to be registered must serve or redirect to a\n valid website (e.g., not a parked domain) that belongs to the sender. For\n example, if the sender email address is `noreply@mail.example.com`, then\n `https://example.com` must serve the website. The website must be accessible\n worldwide without needing an IP filter."]]
