Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to start work on ahoy_email #17

Closed
eveerababu-nyros opened this issue Oct 10, 2014 · 11 comments
Closed

How to start work on ahoy_email #17

eveerababu-nyros opened this issue Oct 10, 2014 · 11 comments

Comments

@eveerababu-nyros
Copy link

I followed the same but I could able to migrate and I got table called ahoy_messages and when I send any mail then, fields in the ahoy_messages table were updated, but when I read the mail in gmail/yahoo open_at field is not updating. Can you please say me where were I went wrong

@ankane
Copy link
Owner

ankane commented Oct 10, 2014

It could be a few things. Opens are recorded through a tiny image in the email (an industry standard). You can only see if an email was opened if it has an html part. Also, the user must allow images to loaded.

@eveerababu-nyros
Copy link
Author

Ankane can you give me any suggestions to perform this, like a sample application

@eveerababu-nyros
Copy link
Author

@ankane I did followed same steps mentioned but It could not updated opened at field value, when I read the mail

@ankane
Copy link
Owner

ankane commented Oct 10, 2014

Sorry, totally forgot the most likely cause. If you're on your development machine, there's no way for your email client to connect to your server at localhost with going through a tunnel like ngrok. The easiest thing would be to push your code to a staging environment and test that it works there.

@eveerababu-nyros
Copy link
Author

Really, Ok I will push it into staging and I will test there, Thanks for your support

@eveerababu-nyros
Copy link
Author

I just made my latest work into staging i.e., heroku but stills I am not receiving opened_at

@abhasg
Copy link

abhasg commented Apr 3, 2015

I am facing the same issue, can you please let me know what is the solution?

@rajrishav0711
Copy link

Following is the invisible pixel link which I get in the email :

"https://ci6.googleusercontent.com/proxy/yfZleGdcqENev58hqKrGAjPy4TF0FSrbuQTzX4LOe4K5NxMA1JPg14kF7rBEHhSJsXRuyR1Z_DL6ZwExp6e1CcSWQjJGsFCNtIqW5OEqKMRpDrRy1k9PjI7aNYYDiouEBGXWgnR3Xg=s0-d-e1-ft#http://192.168.1.158:3000/ahoy/messages/HuMrA0D3Xs6IuCcakFLN4qpZS3ZNmBwH/open.gif"

This link doesn't open, and thats the reason for opened_at not getting updated. Can you tell whats the solution?

@ankane
Copy link
Owner

ankane commented Apr 4, 2015

@rajrishav0711 Google proxies content for privacy reasons. 192.168.1.158 is a local IP, which is unreachable by Google. You'll need to configure your email to use a program like ngrok to get around this. https://ngrok.com/

@rajrishav0711
Copy link

@ankane : Thanks. I tried on my staging app, now I get the following error on opening any email

"(No route matches [GET] "/ahoy/messages/48oZwgN8KzH6o5Weis75KxQ4sKjP0WAj/click")"

which I don't get on my local. Entries are getting populated properly on my local.

Solution: #1

@ankane
Copy link
Owner

ankane commented Jul 25, 2016

Cleaning up issues. Please reopen if there's additional information.

@ankane ankane closed this as completed Jul 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants