Solución de problemas de GetResponse

When integrating with GetResponse you’ll be able to confirm that everything is setup correctly by searching your campaigns for the email address your testing with. If you’ve signed up for a membership level or bundle that you’ve associated with campaigns in GetResponse and you’re not seeing the email in the campaign search results then check out the possible causes below:

Proceso de opt-in doble

GetResponse has a double opt-in process which means that they won’t show up visibly on your campaigns in GetResponse until the customer has clicked a ‘Confirm Subscription’ button in an email they receive from GetResponse. The process looks like this:

1. Un cliente se suscribe a un nivel de afiliación o paquete que ha asignado a una campaña en GetResponse.
   
2. MemberMouse informa a GetResponse a través de su API para que añada al cliente a la lista correspondiente.
   
3. GetResponse envía el correo electrónico de confirmación al cliente.
   
4. El cliente confirma su suscripción haciendo clic en el enlace del correo electrónico.
   
5. El cliente aparecerá ahora en los resultados de búsqueda de su campaña en GetResponse.

Sólo es posible desactivar el proceso de doble opt-in enviando un correo electrónico al servicio de atención al cliente de GetResponse y solicitándolo.

Caracteres especiales en los nombres cortos de Bundle

MemberMouse will send along information to GetResponse about which bundles a particular customer has purchased. The method we use for allowing you to identify the bundles on the GetResponse side are short names. You define the short name for each bundle when you’re crear su paquete.

The important thing to understand is that the GetResponse API considers certain special characters as invalid (i.e. hyphens [-]) and if they appear in the bundle short name, then the API call will fail and the customer’s email will not be added to the campaign.  Only lowercase letters, numbers, and underscores are allowed in the shortname for the GetResponse email integration.