Solução de problemas com a 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:

Processo de aceitação dupla

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. Um cliente se inscreve em um nível de associação ou pacote que você mapeou para uma campanha na GetResponse.
   
2. O MemberMouse informa a GetResponse por meio de sua API para adicionar o cliente à lista apropriada.
   
3. A GetResponse envia o e-mail de confirmação para o cliente.
   
4. O cliente confirma sua assinatura clicando no link do e-mail.
   
5. O cliente agora aparecerá nos resultados de pesquisa de sua campanha na GetResponse.

Só é possível desativar o processo de opt-in duplo enviando um e-mail para o atendimento ao cliente da GetResponse e solicitando isso.

Caracteres especiais em nomes curtos de pacotes

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 Criando seu pacote.

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.