v1.8 does not send `track` event about analytics-php

[WhereJuly]

Hi @nd4p90x,
I use Segment via composer. I do it as described in the original Segment PHP docs.

I initialize Segment like this:

class_alias('Segment', 'Analytics');
\Segment::init(MY_WRITE_KEY_HERE);

Then I call the track event like this: \Segment::track($payload) where payload is the data structure as per this gist (see both the payload creation code and the actual depersonalized payload data copied from Segment debugger).

[nd4p90x]

@WhereJuly Thank you for pointing this out. We will investigate this issue and get back with you asap.

[nd4p90x]

@WhereJuly Hello, I am actively testing this issue you have presented. I always try to test in multiple ways before I respond since there are many ways to implement the library. Currently I have tested via straight up scripting, using laravel via the analytics object and via the internal queue process and I am unable to reproduce loss of "track" events. Can you please provide my with the type of implementation you are using and without divulging any proprietary data, can you provide me a snippet of your code which builds out the Segment::track object? I want to do my best to duplicate your setup while testing. Thank you.

[nd4p90x]

@WhereJuly Here is the payload and RAW response that I get using your data in the array, (Hardcoded of course). I know this does not exactly help you, but just so you can see that I am using the latest, via composer in my Laravel test project, and I am getting what is expected. I will continue to work on this for the time being, however, if I am unable to duplicate the issue, I am not sure what the next steps are for me to help resolve your issue.

[WhereJuly]

@nd4p90x I see. Thanks for investigation. I will keep v1.7 for the time being. Just close the issue then if you cannot repeat my error. Thanks again.

[nd4p90x]

@WhereJuly My apologies for not being able to assist you more with the issue. I will keep this issue in the forefront, just in case others customers see the same thing. So far, I have not heard of any others with this issue using v1.8.0. If you do find a solution or a cause, please open a new ticket or re-open this one. Thanks again.